Streamline patient onboarding by querying a QHIN for clinical documentation — remove manual chart retrieval when a patient arrives from an external organization.
Qualified Health Information Network Integration
Objective: Streamline patient onboarding and remove manual data entry by integrating with external organizations via a Qualified Health Information Network (QHIN) query for clinical documentation when a patient is seen at a new facility.
What's Getting Built
- Registration / ADT Trigger (Experience API) — fires the QHIN onboarding query from a patient registration or ADT admit event ·
POST /onboard, LISTEN ADT^A01
- QHIN Integration (Process API) — checks consent and purpose-of-use, matches the patient, and orchestrates directed query and document retrieval ·
POST /Patient/$match, POST /query, POST /retrieve
- Generic FHIR Client (System API) — does the local EHR Patient/$match lookup before any network query and posts imported documents to the chart ·
POST /Patient/$match, POST /DocumentReference
- Kno2 (System API) — submits the directed QHIN participant query and retrieves clinical document references ·
POST /query, GET /documents/{id}
- C-CDA to FHIR Converter (System API) — converts retrieved legacy C-CDA documents into discrete FHIR resources for chart import ·
POST /convert
- Local EHR chart import (target) — receives the reviewed C-CDA or FHIR Bundle committed to the patient chart ·
POST /DocumentReference, POST /Bundle
Prerequisites
- Anypoint Platform org with mutual-TLS or OAuth credential storage.
- MuleSoft Accelerator for Healthcare QHIN integration assets imported from Exchange.
- Active QHIN participant agreement with production query credentials.
- EHR patient registration or ADT admit events to trigger directed queries.
EHR vendor notes
Epic
- Search local Epic chart first via FHIR Patient/$match (MRN + demographics) — skip QHIN query when a confident local match exists.
- Trigger directed queries from Bridges ADT^A01 or registration events; wire Experience API to the same admit workflow staff already use.
- Import retrieved C-CDA via FHIR DocumentReference or HL7 MDM — Epic document types accepted for chart commit vary by organization policy.
Cerner (Oracle Health)
- Local lookup via Millennium MRN and demographics before any network query — route ambiguous matches to HIM instead of querying the QHIN.
- Fire QHIN workflow from PowerChart registration or ADT admit feed; tenant-specific event codes determine when the Process API runs.
- C-CDA-to-FHIR conversion output may need Cerner-specific resource mapping before chart commit — validate with clinical informatics on supported document templates.
Architecture
1. Business requirements
- Query the QHIN for available clinical documents when a patient registers or checks in.
- Retrieve C-CDA or FHIR DocumentReference resources from participating networks.
- Import relevant history into the local EHR without staff searching multiple portals.
- Respect patient consent and TEFCA-required purpose-of-use declarations.
- Log every query and response for compliance and dispute resolution.
2. QHIN query workflow
- Identify the patient using QHIN-demographics or identifier-matching rules.
- Submit a directed query (by patient, by document type, or by date range).
- Receive document location references and retrieve full clinical summaries.
- Parse C-CDA documents into discrete FHIR resources where the EHR requires FHIR.
- Present a summary to clinical staff for review before committing to the chart.
3. API-led connectivity
- Experience API: Triggered from registration or ADT admit events.
- Process API: Consent check, QHIN routing, document retrieval orchestration.
- System API: QHIN participant API (REST/FHIR) and local EHR document API.
- Use the accelerator's C-CDA to FHIR converter for legacy document formats.
4. Consent and identity
- Verify patient consent for network query under applicable policy (TEFCA, state, or local).
- Match patients with sufficient confidence before querying; route ambiguous matches to HIM.
- Handle "patient not found" and "no documents available" without error storms.
- Support opt-out registries where applicable.
5. Error handling and operations
- Retry transient QHIN failures; cache negative responses briefly to avoid duplicate queries.
- Monitor query volume, hit rate, and document retrieval latency.
- Alert when QHIN connectivity degrades during high-volume registration periods.
- Track documents imported vs. manually rejected by clinical staff (quality feedback loop).
6. Security and compliance
- Encrypt PHI in transit and at rest.
- Audit-log every access to and modification of patient data.
- Enforce minimum-necessary access for integration operators and support users.
For additional HIPAA controls, API policies, and reference security patterns, see the MuleSoft Accelerator for Healthcare on Anypoint Exchange.
Exchange assets
Import these from the MuleSoft Accelerator for Healthcare use-case page on Anypoint Exchange:
| Asset |
Includes |
| Patient Summary — EMR Integration Process API |
API specification, Implementation Template |
| QHIN Integration Process API |
API specification, Implementation Template |
| Generic FHIR Client System API |
API specification, Implementation Template |
| C-CDA to FHIR System API |
API specification, Implementation Template (use-case-agnostic converter) |
| Kno2 System API |
API specification, Implementation Template |
| Patient Sync Lightning Web Component |
Source (Salesforce Health Cloud Patient Search LWC) |
Sample payload — FHIR Patient/$match (pre-QHIN local lookup)
POST /Patient/$match HTTP/1.1
Content-Type: application/fhir+json
{
"resourceType": "Parameters",
"parameter": [{
"name": "resource",
"resource": {
"resourceType": "Patient",
"name": [{ "family": "Doe", "given": ["Jane"] }],
"birthDate": "1985-03-15",
"identifier": [{
"system": "urn:oid:1.2.840.114350.1.13.0.1.7.5.737384.0",
"value": "MRN12345"
}]
}
}]
}
Testing and validation
- Search for a known test patient in the local EHR first; confirm QHIN query is skipped when a confident local match exists.
- Query Kno2 for a patient with no local match; retrieve document metadata and confirm purpose-of-use and consent are logged.
- Select a C-CDA document and verify C-CDA-to-FHIR conversion produces a valid Bundle imported into the EHR without duplicate patient creation.
- Simulate "patient not found" and "no documents available" responses and confirm no error storm — brief negative caching only.
Phased rollout
Phase 1 — Connect
- Deploy QHIN Process API, Kno2 System API, and C-CDA-to-FHIR converter; register sandbox QHIN (Kno2) credentials.
- Install Patient Sync LWC in a Health Cloud sandbox and wire EMR Integration Process API to the local EHR test endpoint.
Phase 2 — Map and test
- Pilot new-patient onboarding at one registration desk; complete Testing and validation for local match, QHIN query, and C-CDA import.
- Validate consent, purpose-of-use logging, and clinical staff review-before-commit workflow.
Phase 3 — Production
- Expand to additional registration points and document types; monitor query hit rate and retrieval latency.
- Hand off HIM stewardship runbook for rejected or partial document imports.
Success metrics
- QHIN document hit rate (queries returning at least one document) tracked per registration site.
- Median document retrieval and import time ≤ 10 minutes from user trigger to EHR availability.
- Duplicate patient creation rate = 0 when local EHR match precedes network query per workflow rules.
- ≥ 90% of imported documents pass clinical staff review without full manual re-entry.
Configuration checklist
Before first sandbox deploy, complete the shared Healthcare integration configuration checklist — secure property keys, TLS, OAuth, and credential naming conventions are documented once for all Exchange use cases.
7. Implementation starting point
Download the Qualified health information networks integration assets from the MuleSoft Accelerator for Healthcare on Anypoint Exchange.
Register as a QHIN participant and obtain production credentials.
Configure the System API with QHIN endpoint URLs and authentication.
Wire the Experience API to ADT admit or patient-registration events in your EHR.
Deploy the C-CDA to FHIR converter template for document parsing.
Troubleshooting
- QHIN query returns patient not found — Likely cause: demographics insufficient for confident match or patient opted out of network. Fix: Verify match thresholds, collect additional identifiers, and respect opt-out registry before re-query.
- Document retrieval fails after successful search — Likely cause: expired document reference URL or consent scope insufficient for full C-CDA. Fix: Re-query metadata, confirm purpose-of-use, and refresh Kno2 credentials if token expired.
- C-CDA conversion produces empty FHIR Bundle — Likely cause: unsupported document type filtered by converter. Fix: Check supported C-CDA types list; request alternate document or manual import for unsupported templates.
- Duplicate patient created in EHR after import — Likely cause: local EHR search skipped or low-confidence match ignored. Fix: Enforce local EHR lookup before QHIN query per workflow; route ambiguous matches to HIM.
Deliverable: An end-to-end Mule application that queries a QHIN at patient registration and imports retrieved clinical documentation into the local EHR.