FHIR Endpoints and the HealthToGo Sandbox Client Application

In addition to knowing a data holder's FHIR endpoint, end users will need to use an application that conforms to EMR Direct's public API documentation and Terms in order to make queries at that FHIR endpoint. Patients will choose which app they want to use for this, much like they choose a web browser now to view websites.

For EMR Direct customers wishing to test their phiQuery implementation and in ONC Certification testing, the HealthToGo Sandbox app mimics a third-party client application and makes FHIR queries against an EMR Direct developer's sandbox FHIR datasource. Integration partners can view the actual FHIR queries made to EMR Direct's FHIR server using HealthToGo Sandbox (which we pass on to you through phiQuery) by clicking on the Show Raw Data link, which your proctor will also want to see during certification testing, to match up those queries to the published documentation of the Open API. This Open API is the same "interface" a real end user would experience, through their chosen client application that they make themselves or use from a 3rd party, in the real world.

To handle all possible data categories that can be requested, phiQuery implementers will need to be able to respond to requests for all of the data categories listed in the table of Common Clinical Data Set Elements in Section 5.d of the phiQuery Documentation for Health IT Data Holders document. They will also need to support requests for a CCDA document as per Section 5.e of the same documentation. EMR Direct Interoperability Engine will translate the incoming FHIR requests into phiQuery requests that call the methods described in those two sections (5.d and 5.e) of the phiQuery API documentation.




Did this article answer your question? If not, please contact us.