We work closely with hospital IT, physicians, and software engineers to deliver solutions that are easy to implement and use. For additional information regarding implementation of our products, request a demo today.
Illuminate Computing Environment
Illuminate provides a turn-key server appliance that resides on-premise within the hospital datacenter.
Hospital Compute Requirements
Illuminate requests to work with a hospital IT to establish proper configuration of the hardware. For more details on what's required, request a demo.
Hospital Data Requirements
Illuminate requests a read-only database connection to the EMR reporting database (e.g. Clarity, Millennium) for historical data extraction, and for periodic updates for various data elements. Further detail can be provided once a non-disclosure agreement or contract is in place between the hospital and Illuminate.
Hospital Data Requirements – Backloading
During the implementation phase, Illuminate will query the EMR database and retrieve clinical history for loading into Illuminate. Loading many years of history is an important part of our process, but does not require us to run our AI models over the entire history — this can be decided at a later step. Our query process is designed so as to minimize impact on day-to-day operations.
Hospital Data Requirements – HL7 Outbound
Illuminate uses HL7 to stay current with specific clinical events that are occurring within the EMR. There are several HL7 interfaces are required for proper configuration of Illuminate. For a more details on these connections, request a demo.
The Illuminate system has internal capabilities to transform HL7 data in fields our system needs. This approach allows Illuminate to receive a copy of existing production HL7 flows, minimizing the effort required from Hospital IT. Our implementation team takes each HL7 feed and maps it into the appropriate fields in Illuminate. Through this repeatable and proven process, all that is needed from the hospital side is to duplicate the various HL7 feeds at the Interface Engine and send this copy to the Illuminate server.
Illuminate Remote Access
Illuminate associates will need remote access throughout the life of the contract. To simplify the process of personnel management and to enhance security, Illuminate uses SecureLink. Information can be found at www.securelink.com and is used by most major hospital systems around the world.
We supply a small VM that serves at the internal SecureLink gateway. If the hospital already uses SecureLink, then we can incorporate into the existing installation of SecureLink.
We can also support, but don’t prefer, various VPN (both Point-to-Point and user VPN Client), but this adds complexity in managing passwords and users over the life of the contract.
Illuminate has the option of authenticating users against an Active Directory instance, utilizing LDAP(S). In order to do so, Illuminate would require an LDAP bind string, which will typically be an IP address or hostname of an LDAP server, along with any OU's (Organizational Units) that would be required to make the correct LDAP query.
Desktop Computing Requirements
All of our applications except PatientView™ are browser based. Our strategy as a company is to eventually move all applications to a browser.
ILM Web Applications
Google Chrome (Latest Version)
Firefox (Latest Version)
Microsoft Edge (Latest Version)
Apple Safari (macOS 10.10 – Yosemite)
ILM PatientView™ Desktop App
Windows 10, .Net Framework 4.5 or newer, Processor 1.GHz, RAM: 2GB