When any client has the Nimbo-Cirrus connection enabled through the API configuration (see Maintenance API Configuration) ,they will be allowed to synchronize encounter information, patients and their vital signs, diagnoses, clinic history, products and services requests, policies and thus allowing clinicians to communicate Nimbo consultations with Cirrus.
Nimbo Cirrus Connection
Data shared from Nimbo to Cirrus via API connection.
Patient Information
If this API connection is active, we will be allowed to send from Nimbo to Cirrus all of the following details about the patients and their Nimbo encounters :
Patients
Appointments
Encounters
Allergies
Diagnoses
Vital Signs
Prescriptions
Service Orders
Procedures
Clinical Record
You can see this after syncing the patient with Cirrus, where an alert will let you know that this patient is in Cirrus :
Patients
MRN
Name
Sex
DOB
ID
Phone number*
Demographic Information
Insurance Information
Responsible Information
Employment Information
Note : Fields in bold letters are mandatory.
*If Phone number is not entered during Nimbo's patient registration then this patient may not be sent to Cirrus since phone number is mandatory for Cirrus processes.
Allergies
Any drug allergies that a patient may have will be also sent to Cirrus as active allergies.
If you go to Cirrus, you will be able to see the drug allergies on drug alerts, on Allergies tab from Patient Registration, Allergies option from Physician Dashboard and in the Electronic Patient Record :
Medical History
Same as Allergies, the patient medical history will be sent to Cirrus and it can be viewed in the Electronic Patient Reccord of this patient.
Vital Signs
Nimbo consultations also allows physicians to enter vital signs of the patient during the encounter. This information will be synced with Cirrus so it will not be need to enter this information on both systems.
Some vital signs you can enter are, for example :
Height
Weight
Body Mass
Temperature
Respiratory Rate
...and more.
Vital signs will be recorded in the Electronic Patient Record and in Vital Signs option from both Physician Dashboard and Nurse Dashboard.
Diagnostic
Any diagnostic added during the appointment process will be synced with Cirrus. Diagnoses from Nimbo will always appear as active on Cirrus.
Example :
Diagnosis in the Electronic Patient Record (you can also view them in the Diagnosis History from Physician/Nurse Dashboard) :
Encounter Information
Encounter details such as MRN, physician, specialty, encounter notes, physician notes, date and hour and follow up information will also be sent to Cirrus.
You can view the encounter information in Current Encounters window :
Note :
If the consultation has a price configured and their physician has this product assigned, Cirrus will create the charge automatically (by taking product and product price information).
Prescriptions
With this integration, prescriptions generated during encounters in Nimbo that are sent to Cirrus will be saved in Cirrus for later administration, delivery to the patient, or printing in patient account reports.
The prescription-related information sent to Cirrus is as follows:
Generic Drug name
Dose
Frequency
Via
Duration
Comments
Diagnostic
If you click on Send to pharmacy, they will appear also on Pharmacy (Cirrus).
Lab & Imaging Service Orders Requests
Lab and Imaging requests will be sent to Cirrus. Cirrus will then create the HL7 message if configured (see configuration at the end of this article) :
Nimbo Cirrus Interactions Log
In addition to all the information related to the patient account, a record of interactions between Nimbo and Cirrus will also be saved in the Electronic Medical Record (Patient Log tab), here you can see the event change log of the encounter.
Catalogs
In addition to the patient clinical information, Nimbo communicates with Cirrus to send details about other clinical details such as :
Also Generic Drugs that are prescribed and Services requested must be synced through the catalogs (see Cirrus-Nimbo connection section).
Cirrus-Nimbo Connection
Information shared from Cirrus to Nimbo with API integration.
Communications between Cirrus and Nimbo is in both directions. For example, you will be able to enter patients in Cirrus and schedule medical appointments in Nimbo for these patients once their information is imported. The same will happen when patients and users are created in Cirrus.
Data sent from Cirrus to Nimbo is the following :
Patients
Paid Encounters (if configured)
Users (creation and connection)
To connect a physician in both Cirrus and Nimbo you must perform the following steps :
Create physician user in Cirrus.
Create physician user in Nimbo.
Go to My Account, then select Organization tab, select member in Members of you organization and click on Edit.
Click on Sync with Cirrus to login and connect this user.
Admin users (only for communications between Nimbo and Cirrus )
If a patient is in Nimbo, you will see this in Patient Registration window, right under the MRN of this patient :
Patient Exportation
From Cirrus, you can export one or multiple patients to Nimbo via our Patient Exportation window.
See more details in the button :
Catalogs
Cirrus catalogs for Generic Drugs (not their brands), Lab, Image and other services, Business Partners and Policies will be copied by a manual process to Nimbo so users can use them as well during their consultation processes.
Settings
The settings needed for enabling this integration are the following :
Maintenance API Configuration
Configurations for connection Cirrus and Nimbo.
Fee Charges Configuration
Configurations for creating charges when a physician starts their appointments.
First, you must go to Physician window and perform a physician user search. In Physician's organization information you must enter a consultation (configured already as a product with price) :
And in Office visit configuration you must check the Fee charges box to generate charges when an appointment starts :
HL7 Messages Configuration
To enable the HL7 messages on Cirrus, you must check the Requires HL7 ADT Message in the Configuration of Medical Record window for communicating patient's demographics and more visit information.
Here, you can also check the Requires HL7 MFN Message, which will display messages when the whole master file gets replaced as a whole by another document.
We hope this improves your Cirrus experience. Remember to share this information and ask for help if you need it.
Date: November 27, 2023.