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

Conformance & Certification Expectations

MERT defines practical and testable conformance expectations for Sender and Receiver roles.

Sender Conformance Test

Given a source system that contains values for MS elements:

• When exporting a resource,
• The MS elements SHALL be present in the generated FHIR instance,
• With correct datatype and semantic meaning.

Receiver Conformance Test

Given an inbound resource containing MS elements:

• The Receiver SHALL persist the clinical meaning of the element within the newly created import chart or equivalent isolated data structure.
• The Receiver SHALL be able to:
  • Display the information, OR
  • Make the information retrievable through system audit, API, or export, OR
  • Include the meaning in subsequent outbound exchange.

Structured coding preservation is encouraged but not mandatory.

Multi-System Considerations

MERT acknowledges that semantic degradation may occur when exchanging data across heterogeneous systems.

Conformance requires preservation of clinical meaning, not guaranteed preservation of original structured coding.

Systems claiming MERT conformance SHALL document known limitations in structured data preservation.

Receiver Transaction Lifecycle Test

Re-Run Before Finalization

Given a TransactionID that fails prior to finalization:

• When the TransactionID is re-run,
• Previously successful records SHALL be marked as Skipped,
• No duplicate records SHALL be created.

Re-Run After Finalization

Given a finalized TransactionID:

• When a re-run is attempted,
• The system SHALL reject the request with an appropriate error indicating the transaction has already completed.

Credential Expiration and Revocation Test

Given an active TransactionID:

• When more than seven (7) days have elapsed since issuance,
• The Sender SHALL reject authentication or retrieval attempts.

Given a revoked TransactionID:

• When a retrieval attempt is made,
• The Sender SHALL reject the request.

The Sender SHALL record expiration and revocation events in the audit log.