Technology Requirements Met
You don't have to worry about HL7 or any other "standard"
There is an integration standard called HL7.
Actually there are 8 versions of HL7 and you would get mired in the muck if you had to worry about all of them.
The multiple HL7 versions and other "standards" are our problem to deal with.
We provide you with one standardized JSON structure to implement in your software.
Do that and it will work the same way whether the EHR is on-site at the facility or in the cloud.
Note: If you are comfortable with HL7 and want to send and receive HL7, Q supports that as well.
Send and Receive Patient Data
You have implemented our standardized JSON structure. Great! [now what?] Well your software can receive this JSON structure for all messages sent from the EHR.
This includes new/updated patient information, new/updated/canceled appointments, clinical documentation, observation results, and the whole gamut of EHR messaging.
Your software can send any message type that it can receive. Q will poll your API endpoint for JSON messages destined for the EHR (using a schedule that you determine).
Prep for FHIR
FHIR is yet another integration standard that is anticipated for publication sometime in 2017.
Q is forward-compatible with FHIR because it keeps itself updated with the latest modules for FHIR and other standards.
This means that you don't have to worry about FHIR - we do.
Simply implement our standardized JSON structure and you will be ready for FHIR without ever changing your software.