Isabel can be integrated on many different levels into the Electronic Medical Record (EMR) bringing the power of the differential checklist into the clinicians’ workflow. No matter which EMR you have, there is a way to make Isabel accessible from within the EMR. Isabel supports standards including query string and HL7 Infobutton and complete API embedding using JSON or XML.
Level 1: Basic Integration – Uses Isabel’s Interface with auto-login
This allows Isabel to be launched from the EMR via a button or menu function providing automatic login. After login the Isabel DDx’s key features are available using the Isabel interface which requires manual entry of demographics, clinical features and generating the differential.
Level 2: Query String and HL7 Infobutton
Isabel supports query string integration. This allows the system to extract the demographics and clinical features from the EMR, to pre-populate Isabel and generate a differential automatically.
Isabel also utilizes HL7 Infobutton interoperability standards. When Isabel is launched from a problem or chief complaint via Infobutton in an EMR, demographics are automatically extracted along with the problem or chief complaint and sent to Isabel for differential generation. Isabel also supports HL7 Infobutton integrations that can accommodate the extraction of multiple clinical features. The differential results are returned utilizing the Isabel user interface, which allows direct access to all Isabel’s features, enabling the clinician to research and correlate their differential.
Isabel also has the ability to send items from the differential list back to the EMR including the disease name, SNOMED code and ICD9/10 codes.
Level 3: Isabel API
A distinctive feature of Isabel is that we offer a complete set of API’s allowing Isabel to be fully embedded into any system. This allows the provider to utilize their own user interface style and design. The complete suite of Isabel features is available in either JSON or XML. Key clinical features and demographics are automatically extracted from the patient’s record. The API can be used to create a uniform user experience on multiple platforms including desktop computers and mobile devices.