Patients should not need to move healthcare data manually
Medical information is often scattered across hospitals, specialists, labs and other healthcare organizations.
Traditionally, bringing that information together could involve:
- requesting records
- downloading PDFs
- faxing documents
- re-entering medical history
Modern interoperability offers a better model.
Patients can increasingly authorize applications to access eligible healthcare information electronically.
A key part of that architecture is SMART on FHIR.
What is SMART on FHIR?
SMART on FHIR combines two important concepts:
FHIR provides standardized healthcare data structures.
SMART provides an authorization framework for healthcare applications.
Together, they allow an application to request access to specific health information without requiring the application to store or know the patient’s healthcare-system password.
A familiar authorization experience
The pattern is similar to other secure account-connection experiences.
A patient chooses to connect a healthcare organization.
The patient is redirected to that organization’s authentication system.
The healthcare organization confirms identity.
The patient authorizes the requested access.
The application receives a token representing that permission.
The application can then retrieve permitted healthcare resources.
The workflow is conceptually:
Why OAuth matters
SMART typically relies on modern authorization standards such as OAuth 2.0.
That matters because credentials stay with the healthcare organization.
HealthCheck does not need to ask the patient to hand over their EHR password.
Instead, the healthcare organization decides whether access is allowed and issues authorization accordingly.
That is a much stronger security model.
What information can be accessed?
The exact information depends on the connected healthcare organization and the permissions granted.
FHIR resources may include information such as:
- demographics
- conditions
- allergies
- medications
- laboratory results
- immunizations
- encounters
- diagnostic reports
- procedures
Different organizations may expose different resource sets and historical depth.
Patient access is only the first step
Retrieving data is technically important.
Making it understandable is the harder product problem.
A patient may connect three healthcare organizations and receive:
- duplicate conditions
- repeated medications
- overlapping lab records
- differing terminology
- multiple provider identities
A health-record platform needs to organize that information into a coherent patient view.
The HealthCheck longitudinal record
HealthCheck is designed to bring authorized healthcare information into a longitudinal health record.
Instead of organizing information by which hospital produced it, the experience can organize information around the patient.
Examples:
Timeline — encounters, tests, medications and major health events.
Labs — results across connected sources.
Medications — current and historical prescriptions.
Conditions — consolidated clinical history.
Care Team — clinicians and healthcare organizations.
Diagnostics — laboratory and connected diagnostic results.
Connected data becomes useful data
Once healthcare information is available in a normalized context, it can support additional workflows.
For example, HealthCheck can potentially use authorized information to help the patient:
- prepare for an appointment
- review medication history
- understand a laboratory result
- identify overdue preventive care
- avoid repeatedly entering known information
- provide context for a telehealth encounter
The goal is not simply to create another medical-record viewer.
It is to make the health record useful throughout the healthcare experience.
AI introduces additional governance requirements
Longitudinal records can also provide valuable context for AI-assisted healthcare navigation.
But an AI assistant should not automatically receive unrestricted access simply because the data exists.
The system must consider:
- patient authorization
- role
- task
- data classification
- minimum necessary access
- policy
- auditability
This is where HealthCloudOS’s governance layer becomes important.
From portal-centric healthcare to patient-centric healthcare
Healthcare portals are typically organized around institutions.
A patient may have one portal for a hospital, another for a specialist and another for a laboratory.
SMART on FHIR supports a different architectural direction.
The patient can increasingly choose an application and authorize healthcare organizations to contribute information to it.
That shifts the center of gravity:
This is one of the most important changes interoperability can enable.