Implementing phiQuery using CCDA-to-FHIR Integration

Implementing phiQuery via the CCDA-to-FHIR Parser of the EMR Direct's Interoperability Engine® allows for a simpler and quicker path to phiQuery integration. CCDA-to-FHIR can be preferable over implementing each of the individual phiQuery listener methods required for integration, especially when a suitable CCDA is readily obtainable and every user and/or client application is always authorized to access every category of data for the patient to which they are authorized.

If an implementer requests that their account be configured to use the CCDA-to-FHIR Parser, data category requests for data other than the CCDA are handled by the parser, which first retrieves the CCDA from the datasource and then parses the CCDA to extract the granular data elements for the requested data category. The FHIR response to the client application is generated by real time parsing of the CCDA returned by the Data Holder. Integrations using Interoperability Engine’s CCDA-to-FHIR Parser do not need to implement all the category-specific data request methods in order to leverage support for the ONC 2015 Edition g.8 data categories; thus, because developers only implement the getCCD method and skip implementing every data category request, CCDA-to-FHIR enables rapid phiQuery integration and helps developers to quickly get to a proof of concept.

Please note that there is not an exact mapping between CCDA and FHIR formats. Therefore, if developers elect to use the optional CCDA-to-FHIR parser capabilities, they are responsible for thoroughly testing all variations of CCDAs that may be returned by the system to ensure that all required data elements can be properly handled by the Parser. Please refer to the phiQuery API Documentation for more information on the methods the server will use to authenticate a user and request a CCDA from the Data Holder. Contact support@emrdirect.com for additional information or to evaluate the phiQuery CCDA-to-FHIR parser.

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