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

Testing and Validation

This section defines validation and verification expectations for systems claiming MERT conformance.

Testing includes profile validation, terminology validation, workflow validation, and lifecycle behavior verification.

---

1. Profile Validation

All exchanged resources SHALL:

• Conform to their declared MERT profiles.
• Pass validation using a FHIR-compliant validator.
• Satisfy cardinality, datatype, and invariant constraints.

Validation errors SHALL be treated as record-level failures.

---

2. Terminology Validation

For elements with Required bindings:

• Codes SHALL validate against the specified ValueSet.

For Extensible bindings:

• Codes SHOULD validate against the specified ValueSet.
• If alternative codes are used, clinical meaning SHALL be preserved.

---

3. Sender Conformance Tests

Sender systems SHALL demonstrate:

• Generation of non-predictable TransactionIDs.
• Seven (7) day maximum credential validity.
• Immediate rejection of expired or revoked TransactionIDs.
• Enforcement of authorization scope.
• Logging of export initiation and revocation events.

---

4. Receiver Conformance Tests

Receiver systems SHALL demonstrate:

• Acceptance of Must Support elements when present.
• Preservation of clinical meaning.
• Source identifier preservation.
• Prevention of duplicate records during re-run.
• Rejection of TransactionID re-run after finalization.

---

5. Transaction Lifecycle Tests

Re-Run Before Finalization

Given a failed TransactionID prior to finalization:

• Previously successful records SHALL be marked as Skipped.
• No duplicate records SHALL be created.

Re-Run After Finalization

Given a finalized TransactionID:

• Re-run attempts SHALL be rejected.

---

6. Audit Verification

Implementations SHALL demonstrate:

• Export initiation logging.
• Authentication attempt logging.
• Retrieval logging.
• Revocation logging.
• Import outcome logging.

Audit logs SHALL not expose passphrases.

---

7. Test Evidence

Systems claiming MERT conformance SHOULD provide:

• Validation reports
• Sample exported resources
• Import logs demonstrating lifecycle behavior
• Documentation of terminology handling