I applied the torrent concept to healthcare information exchange and developed CareFabric from that starting point. This page explores where the idea could go next: from simulated workflows to a focused implementation, then to a wider network of participating organizations.
A natural next step is to bring one exchange to life: a requester discovers a participating source, obtains authorization and receives useful clinical context. Starting with one handoff makes the peer-to-peer pattern tangible.
A clinic requesting recent laboratory results is a clear first example. Connect the two participants through PeerNodes, agree the exchange package, and follow the request from patient matching through delivery and audit using approved test data.
| Stage | Working scope | What each stage establishes |
|---|---|---|
| 1 · Establish the foundation | Document or summary exchange, identity handling, local policy, audit and support ownership. | Approved workflow and data contract; successful and denied paths demonstrated; recovery and escalation exercised. |
| 2 · Add structured depth | Selected FHIR resources, terminology mapping and receiving-workflow integration. Optional reviewed AI assistance. | Conformance results for the selected guide; usable clinical context; measured review burden and data quality. |
| 3 · Expand deliberately | More participants, profiles and event-driven exchange where justified. | Repeatable onboarding, capacity and failure testing, version compatibility and funded operational ownership. |
A first implementation would establish a baseline and follow the complete handoff, using the measures below to understand response time, data quality and operational effort.
Longer-term exploration could look at duplicate investigations and patient outcomes through an appropriate clinical evaluation, alongside the exchange measures.
The peer network brings together shared coordination and local ownership. Developing it means connecting the services, people and operating processes behind each participating PeerNode.
Registry, policy publication, discovery, trust services and audit intake form the shared coordination layer. An operating team would own service availability, support and incident response.
Each participant brings its local adapters, identity workflows, sharing rules and review team. Reusable contracts and guidance would make that work easier to repeat across sites.
A sustainable operating model would cover shared services and the effort of participating sites, while keeping clinical authorization tied to its approved purpose. Funding arrangements can be developed for the setting in which the network operates.
The focus is clinical information exchange. Existing clinical systems remain the source of records, while CareFabric connects the information needed across them.
| Design need | Approach in the blueprint |
|---|---|
| Match the patient across sources | Validated identity rules, reviewable ambiguity, denied-path tests and incident investigation. |
| Protect discovery and audit information | Minimized fields, restricted access, retention limits and privacy review of the locator and audit data. |
| Maintain authorization and recovery paths | Redundant services and tested recovery. Fail closed for new authorizations; document the handling of already-issued grants and emergency workflows. |
| Protect access grants | Short-lived grants plus enforced sender constraints where selected; key rotation, revocation and replay testing. |
| Protect content across the relay | End-to-end encryption across the relay, separated keys, retention controls and verification of what the operator can observe. Network metadata can remain visible. |
| Keep participants and policies compatible | Versioned contracts, compatibility tests, controlled policy rollout and rollback. |
| Deliver the audit trail reliably | Durable local buffering, monitored delivery, capacity testing and a defined rule for when exchange must stop. |
| Make exceptional actions reviewable | Explicit review, restricted roles, event-level evidence and accountable follow-up. |
| Keep integration portable and sustainable | Portable contracts and data, documented exit paths, multiple implementation options and measured support costs. |
CareFabric is designed to connect existing EMR and other clinical systems through local adapters and a PeerNode. The integration uses the interfaces available at each participating site.
Yes. A group can begin with its own branches and a shared trust function, then extend participation through agreed governance and compatible exchange contracts.
The project includes the architecture blueprint, interface concepts, workflow simulations and 28 recorded walkthroughs. These show how the idea works and provide a starting point for further implementation.
Standards provide a common language for clinical information, identity, authorization and audit. Each implementation would select the applicable profiles and align its operating rules with the requirements of its setting.
An existing platform could provide adapters, routing or other PeerNode capabilities. CareFabric describes the responsibilities and connections, leaving room to build on systems an organization already uses.
CareFabric is what grew from applying the torrent concept to healthcare information exchange. I used architecture as code with AI to develop the idea into a blueprint and make its workflows visible.
If the idea interests you, I’d love to hear how you would use it, which workflow you would explore first, or where you see a connection to your own work.
Explore the architecture, watch the simulations, or get in touch to continue the conversation.
Review the technical sources and standards or return to the project overview and healthcare impact.