HEALTHCARE CONNECTION INFRASTRUCTURE
A proposed connection layer for clinician, provider and insurer contexts, built around purpose, source and authorized scope.
A CONNECTION LAYER
Keep your sources together.
Choose who to include.
Primary care · Specialist clinics · Diagnostic clinics · Rehabilitation · Your documents
Illustrative flow. Sharing begins with your selection and review. A visible source is not a live connection.
KEEP YOUR SOURCES TOGETHER
The original.
And everything that explains it.
Record dates, import dates and your own notes play different roles. Keep them readable beside the information they describe.
Read about source contextOriginal document
After-visit summary
Uploaded PDF · Original retained
- Document date
- 14 Oct 2026
- Added to records
- 16 Oct 2026
- Source status
- Original document · Not amended
THE CONNECTION CONTRACT
| Field | Why it belongs beside the data |
|---|---|
| Source identity | The originating organization, document or device, plus its source identifier and revision. |
| Time | Collection or encounter time, report time and import time describe different events; retain each. |
| Exact meaning | Preserve the value, unit, comparator, method, specimen and source interval when supplied. |
| State | Preliminary, final, amended, partial, missing and unsupported must stay distinguishable. |
| Access scope | Record the authorized recipient, role, purpose, information types and relevant expiry. |
| Recovery | A source conflict or interrupted handoff needs an accountable next action, not a silent merge or assumed success. |
A technical connection does not itself authorize clinical, payer or pharmacy actions.
The proposed infrastructure may support insurer contexts. Reporting data, eligibility, coverage decisions and claims are separate functions; no live eligibility check, claim submission or insurance coverage is established here.
A developer specification or partner catalog will need verified formats, authentication, authorization, error contracts and support ownership before publication.
Explore integration boundaries