I applied the torrent concept to healthcare information exchange, and CareFabric is the architecture that emerged. The starting question was simple: could a care team discover and request the information it needs from participating peers while each organization keeps custody of its own records?
I adapted the peer-to-peer idea around a patient journey: discover relevant sources, request authorized information from them, and bring their responses together at the point of care. A laboratory, a pharmacy and a hospital can each contribute the context they hold.
I developed that idea through architecture as code with AI, turning it into diagrams, service responsibilities and workflow simulations. CareFabric adds the healthcare-specific structure around the exchange: patient identity, consent and policy, trusted participants, and an audit trail.
About the project: CareFabric is a concept-stage architecture blueprint, presented through diagrams, interface concepts and 28 simulated workflows.
The torrent concept supplied the inspiration for discovering and exchanging information across peers. CareFabric develops it into a governed healthcare exchange using clinical data standards and purpose-specific access. The result is a connected view of care built from information held across participating organizations.
With the right care and reporting workflows, this foundation could also help reduce avoidable crowding in clinics and hospitals and support pandemic preparedness and control.
I started with a familiar gap: a patient’s care crosses organizations, while each organization holds only part of the story. That made healthcare a compelling place to explore the peer-to-peer idea.
A clinic may need results from an external laboratory, medication history from a pharmacy and a report from a hospital. CareFabric gives those requests a common path, from discovering the source to receiving the response in the clinician’s workflow.
Imagine a patient visiting a clinic away from her usual provider. The clinician needs recent laboratory results, medication history and an imaging report held elsewhere. In the CareFabric workflow, those sources contribute authorized context to the same encounter, with provenance for the clinician to review.
Staff identify likely providers, request records, follow up and reconcile what arrives. Missing or delayed context consumes attention during the encounter.
The clinic verifies identity, discovers eligible sources, obtains scoped authorization and retrieves approved content into its local workflow. Exceptions enter a visible review queue.
This is the idea made concrete: one encounter, several contributing peers, and a coordinated view of the information available. Each response carries its source and context; each request has a defined purpose and a recorded decision.

The same exchange pattern opens further possibilities: moving useful information to the people who need it, supporting follow-up closer to the patient, and connecting participating sites to authorized public-health reporting workflows.

For example, a clinician could review an external laboratory result during a planned remote follow-up, reducing a journey made just to carry a report. This is one application I would explore alongside the service-design considerations in WHO’s telemedicine implementation guide.
During an outbreak, agreed lab and case-reporting interfaces could help authorized public-health teams receive timely, standardized information from participating sites. Those teams can validate signals, investigate unusual patterns and coordinate follow-up. This is consistent with the early-warning and intervention-monitoring purposes of public-health surveillance described by WHO.
An extension for surge planning could bring together approved activity summaries and separately integrated facility-capacity feeds. The same pattern applies: discover the right sources, exchange the agreed information, and present it to the team coordinating a response.
Extend the pattern with a clear purpose. Public-health reporting would have its own approved recipients, data fields, retention rules and correction process. Aggregate reporting and identifiable case reporting would each follow the access rules agreed for that workflow.
The ambition is to help information move with the care journey and shorten the path from a report to a coordinated response. I see CareFabric as part of a wider service design that brings together people, clinical workflows and digital tools, informed by resources such as WHO’s digital-health guidance.
I’m sharing CareFabric to show where applying the torrent concept led me: from a peer-to-peer inspiration to a healthcare architecture and a set of working simulations. If that connection interests you, explore the blueprint, watch the workflows, and let’s connect.