DFT Ballot - This specification is currently in ballot review and subject to change. It is not ready for limited roll-out or production level use. For a full list of available versions, see the Directory of published versions
Table 4 – Interoperability Recommendations for Use Case 4: Query and Retrieve Data
| USE CASE ACTOR | SERVICE SUPPORTED | TECHNICAL ACTOR | Implementation Expectation | PROFILE/STANDARD |
|---|---|---|---|---|
| Consumer | Authenticate User | Client (e.g. EMR) | Optional | Internet User Authorization (IUA) |
| Consumer | Retrieve Patient Identifier | Client (e.g. EMR) | Optional | Use Existing Standard Employed by the Clinical System |
| Consumer | Retrieve Patient Identifier | Patient Demographic Consumer | Optional | PDQm |
| Central Infrastructure | Return Patient Identifier | Patient Identity Registry | Optional | PMIR |
| Consumer | Query and Retrieve (Patient Identifier) | Client (e.g. EMR) | Expected | Use Existing Standard Employed by the Clinical System |
| Consumer | Query and Retrieve (Patient Identifier) | Data Consumer | Expected | CA:FeX 2C: Search Resource |
| Responder | Return Data Bundle | Data Responder | Expected | CA:FeX 2C: Search Resource |
Note: These tables are not exhaustive and do not include all components required for a robust production deployment.
Aspects such as security, privacy, consent enforcement, and patient identity resolution are implementation-dependent and governed by jurisdictional or organizational policy.
Legend
- Expected – Represents interactions that are typically expected in baseline implementations of CA:FeX.
- Optional – Represents interactions that may apply based on local context, system configuration, or jurisdictional policy.