Determine phiQuery Deployment Model
If FHIR services are being enabled for multiple practice organizations through a phiQuery listener deployment, the implementer will need to choose a deployment model that matches how patient data is accessed from within the EHR. The implementation can either be designed to have the phiQuery listener run in a centrally-hosted single instance secured by the implementer that passes data requests to a single vendor-wide or multiple disparate practice datasources (i.e. the EHR operates one listener that services all its customers), OR the listener can run at multiple disparate locations or other distinct instances, one for each practice-specific datasource (i.e. each datasource corresponds to a different instance of the phiQuery listener).
Depending on how data is stored and what makes sense for the system, the integrator will need to determine the most appropriate phiQuery listener deployment model and let us know which of the above models is preferred. With the single listener approach, if patient identifiers are unique across your enterprise and ability to control client access at the practice level will never be needed, the datasource name can be system-wide (this assumes a common patient database) but the default is to have one listener per datasource and one datasource per healthcare organization (and this is required if each patient database is separate). The datasource name in a particular request is passed back to the listener so the implementer can determine the right database to query.
Please refer to the phiQuery API documentation, "How do I deploy my PhiQueryConnector implementation?" section 3.h in the FAQ, for more information on the phiQuery deployment model. Contact EMR Direct in advance of your production deployment to inform us of your desired approach, so we can set up the authentication method you will use for production during your sandbox evaluation.
Did this article answer your question? If not, please contact us.