Close episode
HIS/EMR retains episode ID and component inventory.
MOBILE-ID · TRUSTED LTANS
Healthcare
Preserve finalized treatment records with linked results and consents while restricting access to health information.
Problem and records to preserve
Records require integrity preservation alongside strict control of sensitive health information.
SYNTHETIC CASE
Synthetic care-episode record set
HEALTH-SYN-001| Element | Illustrative scope |
|---|---|
| Decision makers / users | Records managers, clinical leadership and healthcare IT |
| Source system | HIS / EMR / results system |
| Revision | Post-finalization additions retain approver, reason, episode link and prior record. |
| Record relationship | Supplemental results link the episode and frozen revision. |
Sector-specific record journey
Check components
Reconcile results, consents and large files against inventory.
Preserve with access control
Separate clinical, administrative, verification and export rights.
Retrieve scoped content
Bind purpose, approval and scope to each request.
Delivered artifacts
| Recipient | Artifact |
|---|---|
| Source system | Intake receipts, source/revision-to-archiveId/jobId mappings and per-item errors. |
| Package recipient | Authorized episode package, manifest and missing-component list. |
| Record owner / operations | Completed/outstanding inventory, applied decisions and report references; no automatic legal conclusion. |
Rights, retention and deployment
Separate clinical, storage-admin and approved-export permissions.
Large clinical images require agreed size limits, transfer methods and format checks during discovery.
Retention authority and exit
The owner must approve the retention authority and trigger for this record class: A finalized episode of care; documents and consent inventoried per episode.
Sample dossier and tests
Synthetic text files exercise inventory and hashing; they are not signed contracts, real records or ERS/XMLERS.
Download synthetic dossier| Test | Expected outcome |
|---|---|
| Intact | File inventory, size and SHA-256 match the manifest. |
| Missing / changed bytes | The verifier rejects the package without claiming inventory success. |
| Sector business case | Another unit cannot read records without appropriate grants. |
Scope a PoC for this dossier
Test unauthorized access, missing results and key recovery; verify package completeness.
Prepare a sector-specific requestFinalization point and specific acceptance
| Control point | Requirement |
|---|---|
| Source event | A finalized episode of care; documents and consent inventoried per episode. |
| Revision / decision | Post-finalization additions retain approver, reason, episode link and prior record. |
| Test and expected result | Out-of-team access is denied; additions linked to the wrong episode are detected before acceptance. |
Sample inventory/hashing checks bytes only. Authorization, decision and state cases must run in the provisioned test environment before business acceptance.
Source-system handoff record
| Information | Value / decision |
|---|---|
| Record | HEALTH-SYN-001 |
| Source system | HIS / EMR / results system |
| Revision relationship | Supplemental results link the episode and frozen revision. |
| Recipient and output | Authorized episode package, manifest and missing-component list. |
| Rights and authority | Separate clinical, storage-admin and approved-export permissions. |
| Required rejection test | Another unit cannot read records without appropriate grants. |
Sector information is source business metadata, not automatically new REST fields. Agree field mapping and ownership before a PoC.