Current
UDR lineage, UDS exact-state verification, BrowserCarrier and locally grounded document conversation.
Healthcare Bug Light 5 · controlled evaluation · no PHI
Why does a clinical document lose intelligence and provenance when it leaves the system that created it?
Clinical data can move. The trust context around the document often does not. UD proposes a complementary portable document layer—not an EHR replacement.
A medical document should be able to tell you what it is, where it came from, what changed and whether the final state is intact.
Current, pilot and planned
Pilot
One synthetic or de-identified document family without changing the EHR.
Planned / external
Production PHI handling, EHR integration and healthcare workflow deployment are not claimed.
Start with your responsibility
Healthcare CIO
Preserve document trust when information crosses system boundaries.
Open one-page brief →CMIO
Separate clinical authorship, integrity and clinical truth.
Open one-page brief →Healthcare CISO
Verify exact state without mistaking integrity for clinical correctness.
Open one-page brief →Health Information Management
Preserve document identity, source and addenda.
Open one-page brief →Clinical informatics
Connect human-readable documents with structured provenance.
Open one-page brief →General Counsel
Inspect which state was authored, amended and shared.
Open one-page brief →Compliance and privacy
Test provenance without treating architecture as compliance.
Open one-page brief →Payer technology
Carry document identity through payer/program workflows.
Open one-page brief →Utilization management
Know which clinical summary or review state was evaluated.
Open one-page brief →Research informatics
Preserve source and derivation for document artifacts.
Open one-page brief →Interoperability / FHIR architect
Complement data exchange with portable document verification.
Open one-page brief →Patient experience
Make documents understandable without inventing medical advice.
Open one-page brief →Medical records
Preserve original, addendum, final and derived relationships.
Open one-page brief →Government health program technology
Improve notices and inter-organizational provenance without claiming program approval.
Open one-page brief →Healthcare authority cluster
Why Does a Clinical Document Lose Intelligence When It Leaves the EHR?
The originating system can hold workflow, authorship and revision context that a PDF export does not automatically carry. UD proposes a portable document layer for that context.
Read the answer →Transporting Clinical Data Is Not the Same as Transporting a Trustworthy Clinical Document
Structured data exchange moves computable facts. A trustworthy document also needs identity, presentation, provenance, lifecycle state and verification.
Read the answer →Why Provenance Should Travel With the Medical Record
Source, author, creation, revision, addendum and derivation context should remain inspectable when a clinical document crosses systems.
Read the answer →One Clinical Document, Different Readers, Same Source Truth
A patient, clinician, payer or lawyer may need different presentation, but those views should remain tied to the same authoritative facts and provenance.
Read the answer →What Should a Clinical Document Be Able to Prove About Itself?
It should identify its source and state, expose recorded lineage, and let a recipient check whether the sealed bytes remain intact.
Read the answer →Why Patient-Friendly Documents Should Not Require Losing Clinical Provenance
Plain-language presentation can remain grounded in the same source document, with citations and refusal when the answer is not contained there.
Read the answer →