Public programs · architecture paths, not endorsements
Portable provenance can complement—not replace—public-health exchange programs.
These are evaluation paths for synthetic documents. Universal Document has no CMS, Medicare, Medicaid, NHS or government approval.
United States: CMS, Medicare and Medicaid
CMS interoperability rules emphasize standardized APIs and patient access to health information. A bounded UD evaluation could examine a human-readable notice, decision or clinical attachment after it leaves the originating portal: preserve the mandated API and source system, generate a UDR during revision, seal the released state as UDS, and let the recipient verify the exact artifact.
- Keep: payer/provider systems, FHIR APIs, consent, identity, authorization, record-retention and program rules.
- Evaluate: portable document identity, readable provenance, addendum lineage and exact-state verification.
- Do not infer: CMS certification, Medicare/Medicaid approval, HIPAA compliance or clinical correctness.
CMS interoperability policies and regulations
United Kingdom: NHS-type pathways
An NHS-type evaluation should use UK vocabulary and governance: GP records, NHS trusts, integrated care systems, shared care records and patient-facing NHS services. A synthetic discharge letter or referral document could retain its originating system and interoperability pathway while UD is tested only as the portable, human-readable provenance layer.
- Keep: NHS clinical systems, NHS login/identity where applicable, UK information governance, interoperability standards and records-management duties.
- Evaluate: whether a document crossing trust boundaries can carry visible state, source, revision/addendum and integrity evidence.
- Do not infer: NHS endorsement, deployment, DSPT status, UK GDPR compliance or clinical-safety approval.
Safe first exercise
One team, one synthetic document family, fourteen days. No live PHI, no clinical decision-making and no production integration.