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

Sender Responsibilities (Exporting System)

A system claiming Sender conformance to MERT SHALL:

1. Populate Required Elements

Include all elements marked as MERT Required.

2. Populate Must Support Elements

If the source system has a value for an MS element and it is permitted for exchange:

• The Sender SHALL include the element in the exported resource.

If the source system does not capture the data:

• The Sender MAY omit the element.
• The Sender SHALL NOT fabricate values.

3. Preserve Coding

For coded elements:

• The Sender SHALL preserve source codings.
• The Sender MAY include additional mapped codings.
• The Sender SHOULD include human-readable text when feasible.

Senders are not responsible for how downstream systems internally store or represent the data once transmitted.

Senders are not required to guarantee point-in-time immutability of exported data. Retrieval reflects data available and authorized at time of access.

4. Transaction Scope Clarification

Senders are not responsible for:

• Transaction re-run handling within the receiving system.
• Duplicate prevention during re-run.
• Rollback semantics within the receiving system.

Sender conformance applies to generation and exposure of resources, not to lifecycle processing performed by the Receiver.

5. Transaction Credential Management

Senders SHALL:

• Enforce a maximum seven (7) day validity period for TransactionIDs.
• Automatically invalidate TransactionIDs after expiration and reject subsequent authentication or retrieval attempts.
• Provide a mechanism to revoke TransactionIDs prior to expiration.
• Log all expiration and revocation events in accordance with the MERT security requirements.