Demo - The specification is a demo of MERT. For a full list of available versions, see the Directory of published versions

Examples

This section provides illustrative examples of resources and exchange workflows conforming to the MERT specification.

Examples are intended to demonstrate correct profile usage, workflow behavior, and lifecycle handling.

---

1. Resource Examples

Each profiled resource SHALL include:

• meta.profile referencing the MERT profile canonical URL.
• Required elements populated.
• Must Support elements populated when available in the source system.

Example categories include:

• Patient
• Practitioner
• Encounter
• MedicationRequest
• Observation
• DiagnosticReport
• Task
• DocumentReference

Examples MAY include:

• Minimal examples (Required elements only)
• Typical clinical examples
• Edge cases demonstrating Must Support retention
• Examples showing coded and text-only representations

---

2. Transaction Workflow Example

A typical MERT exchange flow:

1. Export initiated by authorized physician.
2. Sender generates:
   • TransactionID
   • Passphrase
   • Host URL
3. Receiver authenticates and retrieves scoped data.
4. Receiver processes resources under TransactionID lifecycle.
5. Receiver records outcomes (Success / Skipped / Failure).
6. Receiver finalizes transaction.

Example logs MAY illustrate:

• Record-level processing results
• Re-run behavior before finalization
• Rejection of re-run after finalization

---

3. Credential Expiration Example

Given a TransactionID older than seven (7) days:

• Retrieval attempts SHALL return an authentication error (e.g., 401 or 403).

Given a revoked TransactionID:

• Retrieval SHALL be immediately rejected.

---

4. Source Identifier Preservation Example

Imported resources SHALL retain the original source system identifier.

Example approaches include:

• Storing original identifier in Resource.identifier
• Maintaining a transaction-scoped reference mapping table
• Persisting original FHIR resource representation

The stored source identifier SHALL remain retrievable for audit or reconciliation.

---

5. Multi-Hop Exchange Example

If System A → System B → System C:

• Clinical meaning SHALL be preserved.
• Structured coding MAY degrade.
• Source identifiers SHOULD remain traceable where supported.

---

Examples in this guide are illustrative and may omit non-essential fields for clarity.