SUJIT PIYUSH PATTNAYAK VP4 PRODUCT CONSULTING
← All projects

Patient record sharing workflow

InstaShare

Patient-owned record sharing

Shows how patients could select, contextualise, and share records with doctors when interoperability rails were incomplete.

Capabilities

Health Records Care Coordination Patient Access

How it works

Workflow overview

Record selection Context annotation Consent confirmation Async share dispatch Provider receipt

Decision spotlight

The product challenge is trust: giving patients control over what they share, why they share it, and how context travels with the record.

Product tradeoff: Data completeness vs. patient trust — sharing has to feel controlled by the patient, not just complete for the provider.


What this demonstrates

Product insight

Before FHIR, patients who wanted to share records across providers had no standard rails. This demo shows that workflow: patient-initiated, record-selected, context-annotated, and async-consultation-threaded — a product pattern still relevant wherever interoperability is incomplete.


Product notes

How I think about this

Product problem

Before modern interoperability standards, patients who needed to share health records with a new provider had no standard pathway. Records were fragmented across institutions, inaccessible in a portable format, or requiring manual fax-and-paperwork cycles.

User / system workflow

Patients select which records to share, add context annotations, and send them to a provider through an async consultation thread. Providers receive structured records and can request clarification before a visit.

My product lens

The design challenge was making the act of record-sharing feel patient-controlled rather than institution-controlled. Framing, vocabulary, and navigation all had to reinforce the idea that the patient owned the record and was choosing to share it.

Why it matters

The patient-owned record model anticipated what FHIR and interoperability mandates later formalised. The product patterns that made it usable — selective sharing, context annotation, async consultation — remain relevant wherever interoperability is incomplete.

What I would improve next

Modern API-first version with FHIR R4 compliance; consent management layer; provider-side structured record ingestion.


More to explore

Pair this with

Explore related demos from the same product menu.

Patient-Owned Health Data

MyHealthRecords PHR

Family health records before mobile-first healthcare

Family-scoped personal health records, trackers, and patient-owned care context.

Patient-Owned Health Data

Mobile Patient Access Suite

Records, Imaging, Helpdesk, and Care Activation

Mobile patient access across records, imaging, reminders, profile, and support.