CareFabric — Architecture

CareFabric began when I applied the torrent concept to healthcare information exchange. This page shows how that inspiration became an architecture: participating peers, discovery of relevant sources, coordinated requests, and local custody of clinical records.

From peer-to-peer inspiration to healthcare architecture

I translated the torrent-inspired idea into three architectural roles. PeerNodes represent participating organizations, a Trust Authority coordinates discovery and the shared rules, and an optional Controlled Relay provides a transport route. Clinical records remain with the systems that hold them.

Trust Authority

Operates the participant registry, policy catalog, discovery service and audit intake. In a group, this is an accountable central function. Across independent organizations, it needs an agreed governance structure.

PeerNode

Provides each participant’s controlled boundary. It adapts local systems, resolves local identifiers, enforces sharing decisions and records activity. The local EMR, laboratory and pharmacy systems remain in place.

Controlled Relay

Provides an optional encrypted transport path when direct connectivity is impractical. Access decisions stay with the exchange services and participating PeerNodes, while the relay has a defined transport role, retention policy and operator responsibility.

The Trust Authority coordinates policy, discovery and audit with two organizations. Their PeerNodes exchange clinical requests and responses directly or through an optional encrypted relay. Local records stay at each organization.
Control interactions and clinical transport are separate. The arrows represent requests and responses; the relay is an optional route. Open full-size image.

Two planes, with different responsibilities

The control plane coordinates participation, discovery, policy and authorization, then receives the audit evidence. The data plane carries approved clinical requests and responses between PeerNodes. Keeping them separate helps make access decisions inspectable and limits where clinical payloads travel.

Privacy is part of the coordination design as well as the clinical exchange. Patient references, record locations and audit trails have scoped access, minimized fields and defined retention rules.

One pattern, two deployment settings

  • Enterprise exchange: connect branches, acquired providers or a diagnostic network under a group governance function. This offers a bounded place to establish the participant contract and support model.
  • Cross-organization exchange: apply a compatible participant contract between independently governed providers. Participation agreements, consent responsibilities, trust anchors and local legal obligations need explicit alignment.

The same PeerNode model can support both settings. Shared agreements on identity, terminology and permitted uses provide the basis for extending the network to further participants.

What I carried forward from the torrent concept

The key connection was discovery followed by exchange with the peers that hold useful information. In CareFabric, the requesting workflow finds eligible sources and can gather different parts of a patient’s context in parallel. I adapted that pattern around authorized clinical requests and existing healthcare systems, with each participant retaining control of its records.

The healthcare layer around the peer network

Healthcare gives the peer-to-peer idea a specific set of responsibilities: identify the patient, establish the purpose of access, apply the sharing rules, and preserve evidence of the exchange. These responsibilities shape the CareFabric workflow.

Connect the right patient across sources

The PeerNode translates local identifiers into the agreed exchange context. Deterministic identifiers and demographic matching can contribute evidence; the network must also handle missing, stale and contradictory data.

FHIR’s match-grade vocabulary distinguishes “certain”, “probable”, “possible” and “certainly-not”. CareFabric uses identity evidence within a review workflow: a probable match may need review, a possible match goes to review, and retrieval follows the applicable access policy.

  • Accepted identity: permit only the retrieval allowed by the clinical workflow and access policy.
  • Ambiguous identity: send the case to an accountable review queue; restrict any discovery to what the governing policy permits.
  • Rejected or unresolved identity: block clinical retrieval and record the reason.

Each participating setting defines matching thresholds and reviewers for its patient population, supported by monitoring of false and missed matches. Staff login assurance and matching clinical records are handled as separate responsibilities.

Give each request a clear scope

A request carries its purpose, authenticated participant, recipient and data scope. The responding PeerNode applies the current policy, local restrictions and consent requirements before releasing approved information.

Short-lived, audience-restricted access can be combined with sender constraints such as mutual-TLS certificate-bound tokens. The responding service enforces the selected binding as part of the request checks.

Make the exchange traceable

Record discovery, authorization decisions, route choice, retrieval and exceptions with correlation identifiers. Both ends need evidence. Store the decision reason and policy version without copying access tokens or unnecessary clinical payloads into logs. Retention, availability and access to those logs are part of the operating design.

The policy model brings together consent information, purpose of use and the applicable authority for sharing. Policy owners define the rules, and the participating services enforce them for each request.

Use AI as a reviewable assistant

AI assistance can help summarize approved records, classify documents or prioritize review. CareFabric gives AI proposals a human review path, a traceable model version and a recorded decision; identity and access remain governed by the exchange workflow.

The core exchange and optional AI assistance are separate parts of the design. This lets the exchange operate on its own and gives each AI capability a defined purpose, review step and evaluation path.

Technical reference

Explore the engineering detail behind the idea: architectural views, exchange contracts, clinical packages and interface concepts. PeerNode and Trust Authority are the names I use for the local and shared responsibilities in CareFabric.

Architecture views and the PeerNode reference

The responsibilities inside a PeerNode

  • Exchange gateway: the exposed contract for approved network interactions; internal databases are not directly exposed to peers.
  • Local adapters: map local records and workflow events to the agreed exchange contract, preserving provenance and identifying unavailable fields.
  • Identity crosswalk: reconcile local identifiers with the exchange context and route ambiguity to authorized reviewers.
  • Policy enforcement: apply the governing decision and the responder’s current local restrictions at retrieval time.
  • Audit and delivery: record decisions and exchanges, buffer events durably and monitor delivery to the agreed audit service.
  • Review hub: give identity, data-quality and optional AI exceptions a named owner and a recorded resolution.

These are responsibilities rather than a prescribed set of processes. A deployment may implement several in one service, reuse an integration platform, or separate them where trust boundaries and operational needs justify it.

Read the architectural views from outside in

The C4 views unfold the design from the people and systems around CareFabric to its services and components. Together they show how the peer-to-peer inspiration becomes a set of connected responsibilities.

System context

C4 system context view of CareFabric and its relationships with clinicians, patients, reviewers, auditors, local clinical systems, external networks and identity services.
The people and systems around the proposed exchange. Open full-size image.

Containers

C4 container view showing Trust Authority services, participant PeerNodes, existing clinical systems and an optional Controlled Relay.
Deployable responsibilities, before deployment-specific technology choices. Open full-size image.

PeerNode components

C4 component view of the PeerNode, including the exchange gateway, local policy enforcement, adapters, identity crosswalk, audit and review functions.
Local enforcement and integration responsibilities at the participant boundary. Open full-size image.

Trust Authority components

C4 component view of the Trust Authority covering registry, policy decisions, discovery, audit, federation coordination and reporting.
Shared coordination functions. Patient-linked metadata in these services remains sensitive. Open full-size image.

The operating design covers both shared services and participant nodes: service availability, certificate lifecycle, policy rollout, rollback and support ownership. Each exchange has a defined path for completion, partial results and recovery.

Standards, versions and terminology crosswalk

Choose a versioned implementation baseline

The examples use FHIR R4 terminology. An implementation baseline brings together the selected FHIR release, implementation guides, terminology and security profiles. Names such as “lab-results-summary” identify CareFabric use cases to map to those standards.

ConcernDesign basis and implementation decision
Clinical exchangeUse the selected FHIR release and published implementation guide for structured data. Use appropriate document profiles where the source is document-oriented.
System authorizationSMART Backend Services provides an OAuth client-credentials pattern with asymmetric client authentication. Patient and purpose restrictions still require explicit policy and server enforcement.
Federated trustThe HL7 UDAP Security guide describes certificate-based trust-community workflows. Select the applicable version and trust agreement; a CareFabric role name does not establish that agreement.
Patient matchingUse explicit evidence and workflow policy around FHIR Patient $match or the appropriate identity services. Do not equate a patient-match grade with a login-assurance level.
Human digital identityNIST SP 800-63-4 supersedes SP 800-63-3 and covers identity proofing, authentication and federation of users. Select assurance requirements for the actual actors and risks.
Consent and policyUse a documented policy model and version-compatible consent representation. FHIR Permission is an R5 resource; it must not be silently assumed in an R4 baseline.
Audit content and transportFHIR AuditEvent represents audit information; IHE Basic Audit Log Patterns supplies reusable patterns. Select the applicable ATNA/BALP profiles and transport explicitly; these are not interchangeable labels for one wire format.
Sender-constrained tokensWhere selected, RFC 8705 defines certificate-bound access tokens. Validate the binding at the resource server; audience checks serve a different purpose.
The standards below provide the building blocks for the exchange contracts.

CareFabric names describe responsibilities

  • Trust Authority: the accountable operating function for participation, policy coordination, discovery and audit. Its responsibilities may span several services and organizations.
  • Policy decision point (PDP): evaluates the relevant rules. A policy catalog is where rules are managed; it is not necessarily the runtime decision service.
  • Policy information point (PIP): supplies attributes such as role, purpose and consent context to the decision.
  • Policy enforcement point (PEP): applies the decision at the participant boundary and enforces the responder’s applicable restrictions.
  • Discovery/locator: identifies eligible holders, data classes and capabilities. Apply access policy to discovery itself and minimize patient-linked metadata.
  • Controlled Relay: transports encrypted traffic under an explicit operator contract. It is not a substitute for either endpoint’s access enforcement.

A deployment can map these responsibilities to its applicable national framework, participation agreements and certification requirements.

Communication flow and illustrative decision examples

An example exchange decision

The following YAML illustrates the information in an exchange decision, using example identifiers. It connects the architectural responsibilities to an eventual versioned API, with signed claims, resource filters and defined responses.

# Illustrative decision model: direct laboratory retrieval
exchange:
correlation_id: demo-visit-001
requester: demo-clinic-node
responder: demo-lab-node
patient_reference: demo-patient-001
use_case: lab-results-summary
purpose: treatment
requested_window: agreed-recent-results
decision:
result: allow
policy_version: pilot-policy-1
identity_decision_reference: demo-reviewed-match-001
sharing_basis_reference: demo-approved-basis-001
grant:
lifetime_seconds: 300
intended_recipient: demo-lab-node
sender_constraint: required-by-pilot-security-profile
permitted_patient: demo-patient-001
permitted_resources: [DiagnosticReport, Observation]
route:
mode: direct
execution:
responder_rechecks_local_policy: true
clinical_response: selected-FHIR-profile
audit_correlation_at_both_ends: demo-visit-001

The example request follows the selected direct route. A relay route uses an approved end-to-end encrypted path, with clinical access enforcement at the endpoints.

# Alternative decision for the same requested exchange
exchange:
correlation_id: demo-visit-002
requester: demo-clinic-node
responder: demo-lab-node
decision:
result: deny
reason: identity-requires-review
policy_version: pilot-policy-1
review_reference: demo-review-002
execution:
clinical_retrieval: blocked
audit_locations: [requester, authorization-service]
audit_correlation: demo-visit-002

The audit model records the events that occur: authorization attempts and decisions in the control plane, and retrieval activity at the peers involved. A denied request remains traceable even when it stops before reaching the responding PeerNode.

Details behind the exchange contract

  • Binding and enforcement: connect the patient, purpose, recipient, sender and data constraints to the checks performed by the responding service.
  • Identity and consent: which service produced the evidence, how fresh it must be, and when a review or revocation invalidates the request.
  • FHIR conformance: validate resources, required fields, coding systems, references and bundles against the selected release and implementation guides.
  • Reliability: timeouts, retries, idempotency, partial results, rate limits, duplicate events and interrupted transfers.
  • Safe references: identify source and freshness, constrain follow-up retrieval and avoid forwarding access tokens to untrusted referenced URLs.
  • Audit: correlate events and preserve the required evidence without logging reusable credentials or unnecessary payloads.

SMART Backend Services connects a client-authentication assertion to token acquisition and uses “system/” scopes for pre-authorized system access. The published security profile provides the detailed authorization pattern for an implementation.

Clinical exchange catalogue

The clinical exchange catalogue

The catalogue shows how one architectural pattern can support many care needs. Each package describes the clinical context to exchange, with its actors, purpose, freshness and resource mappings. Write workflows add command, acknowledgment and duplicate-handling rules.

“patient-summary” — Cross-organization patient summary at the point of care.
Use the document structure and required content defined by the selected International Patient Summary implementation guide.

“encounter-summary” — Visit-scoped data exchange anchored to one Encounter.
Candidate resources: Encounter, Condition, Observation, MedicationRequest, Procedure, ServiceRequest.

“discharge-summary” — Hospital to community handoff at end of admission.
Candidate resources: Composition, Encounter, Condition, MedicationRequest, ServiceRequest, AllergyIntolerance.

“lab-results-summary” — Recent laboratory results.
Candidate resources: DiagnosticReport, Observation.

“lab-orders” — Outbound laboratory order to a reference lab; a separate write workflow, not a retrieval variation.
Candidate resources: ServiceRequest, Specimen.

“pathology-report” — Full pathology report with specimen and microscopy.
Candidate resources: DiagnosticReport, Specimen, Observation, ImagingStudy.

“medication-dispense-90d” — Recent dispense history (default 90-day window).
Candidate resources: MedicationDispense, MedicationRequest.

“medication-list-active” — Current active medications snapshot.
Candidate resources: MedicationStatement, MedicationRequest, AllergyIntolerance.

“prescription-history” — Full prescription history including renewals and substitutions.
Candidate resources: MedicationRequest, MedicationDispense.

“imaging-report-references” — Diagnostic imaging reports plus document references.
Candidate resources: DiagnosticReport, DocumentReference.

“imaging-study-metadata” — Study-level metadata without DICOM bytes.
Candidate resources: ImagingStudy, DiagnosticReport.

“allergies-and-reactions” — Allergies, intolerances, and adverse events.
Candidate resources: AllergyIntolerance, AdverseEvent.

“problem-list-active” — Current active problem list.
Candidate resources: Condition, ClinicalImpression.

“procedures-history” — Past procedures within a window.
Candidate resources: Procedure, ServiceRequest.

“vitals-recent” — Recent vital signs.
Candidate resources: Observation ( category = vital-signs ).

“care-plan-active” — Active care plans and goals.
Candidate resources: CarePlan, Goal, ServiceRequest.

“care-team” — Assigned care team members.
Candidate resources: CareTeam, Practitioner, Organization.

“referral-package” — Referral with supporting clinical context.
Candidate resources: ServiceRequest, Composition, Condition, DocumentReference.

“appointment-context” — Pre-visit context for the receiving clinician.
Candidate resources: Appointment, Encounter, Practitioner, ServiceRequest.

“clinical-document-set” — Generic document exchange (CCD, CCDA, custom).
Candidate resources: DocumentReference, Composition, Bundle.

“immunization-record” — Full immunization history plus recommended-next.
Candidate resources: Immunization, ImmunizationRecommendation.

Versioned packages give participants a shared vocabulary for what they can exchange. A site advertises the capabilities it supports, allowing discovery to connect requests to suitable peers.

Architecture decisions, quality attributes and integration toolkit

The decisions this blueprint takes

DecisionRole in the design
Federated custody with shared coordinationConnects locally held records through shared discovery, policy and trust services.
A PeerNode boundary per participantGives each organization a clear place for integration, access enforcement and lifecycle management.
Separate control and data planesSeparates exchange coordination from clinical transport, with correlated requests and defined recovery paths.
A replaceable, transport-only relayProvides an alternative route across network boundaries while preserving end-to-end protection.
Versioned standards and exchange packagesGives peers compatible exchange contracts and local adapters a defined mapping target.
Explicit identity reviewRoutes uncertain matches to a named reviewer before clinical retrieval.
Discovery with minimized metadataHelps a requester find eligible sources using scoped access to the minimum discovery information.
AI proposals under review and auditPlaces AI assistance inside a traceable workflow with human review and monitoring.
A clinical scope with separate funding decisionsKeeps clinical authorization purpose-based while an operating model supports the network.
A minimum participation floor with staged depthLets participants begin with a shared baseline and add deeper capabilities in stages.
These choices show how I shaped the initial idea into a coherent blueprint.

What to measure as the idea develops

The next implementation step would measure security and privacy controls, audit completeness, recovery, response times and compatibility. Timing the whole request, from authorization to presentation, would show how the coordinated exchange performs.

Building out the integration toolkit

The next toolkit components to develop are adapter guidance, sample data, a conformance suite, reference flows and operational runbooks. Together they would make the PeerNode model easier to implement and extend.

Explore the interface concepts

These interface concepts show how operators could work with CareFabric: follow activity, inspect policies and manage participation. The screens use demonstration data.

Operations overview

Illustrative CareFabric command dashboard showing network health, exchange activity, participant status, operational exceptions and a sample patient journey.
An operations concept: surface exceptions and participation health alongside activity. Open full-size image.

Policy catalogue

Illustrative CareFabric policy catalogue with sharing rules, purpose and trust constraints, policy details, review queues and change history.
A policy concept: make the governing rule and its review history inspectable. Open full-size image.

Participant registry

Illustrative CareFabric participant registry showing organizations, certification and connectivity status, selected-participant details and certificate lifecycle information.
A registry concept: make onboarding and certificate lifecycle visible to operators. Open full-size image.

The interface design follows the same role boundaries as the underlying services, giving each operator the information needed for their responsibilities.

Glossary

CareFabric — The architecture proposal described in this project.

PeerNode — A participant’s controlled integration and enforcement boundary.

Trust Authority — The accountable function operating shared participation, policy, discovery and audit services.

Controlled Relay — An optional transport component for an end-to-end protected exchange path.

EMR / EHR — Electronic medical/health record; the clinical record system and record context used by a provider.

LIS — Laboratory Information System.

RIS / PACS — Radiology Information System / Picture Archiving and Communication System.

FHIR — HL7’s standard for representing and exchanging healthcare information.

Implementation guide — A published set of constraints and usage rules for a particular interoperability context.

Exchange package — A named CareFabric use case that must be mapped to concrete, versioned resource contracts.

MPI / EMPI — Master Patient Index / Enterprise Master Patient Index: identity matching and identifier reconciliation services.

SMART Backend Services — An OAuth-based pattern for system access to pre-authorized FHIR resources.

UDAP — Security profiles for scalable registration, authentication and authorization in a trust community.

PDP / PIP / PEP — Policy decision, information and enforcement responsibilities.

Consent — Information about an applicable consent decision; its interpretation is part of the governing policy.

Purpose of use — The stated reason for requesting access, evaluated alongside the other authorization conditions.

AuditEvent — A FHIR resource for recording audit information.

ATNA / BALP — IHE audit-related profiles; the chosen content patterns and transport must be specified.

IAL / AAL / FAL — NIST assurance levels for identity proofing, authentication and federation of users.

Match grade — An assessment of how confidently a patient record matches supplied identity evidence.

PHI — Protected health information; the applicable definition and obligations depend on the governing jurisdiction.

Sender-constrained token — An access token whose use is bound to a client-held cryptographic key by an enforced mechanism.

Break glass — A tightly governed exceptional-access workflow with explicit accountability and review.

Provenance — Information about where data came from and how it was produced or transformed.

Sources and implementation reading

These references informed the architecture and its possible healthcare applications. They provide further reading for exploring the design and selecting an implementation baseline.

Follow the idea into the workflows

The workflow gallery shows this architecture in motion. If the connection between the torrent concept and healthcare exchange interests you, I’d be glad to discuss the idea and where it could go next.

Leave a Reply