You wrote the record. It should stay with you.
Clinicians should be able to keep and move the records they write. Patients should be able to take their history to the next clinic. Neither should have to pay to get those records back.
Picture a family doctor closing her clinic for the evening. For eight years, she has written a note after each visit: an allergy a patient mentioned, why she changed a dose, what they agreed to check next time. She built that history one appointment at a time.
Now she wants to cancel her software subscription. Before she can, she has to ask: when the payments stop, will she still be able to open the records she wrote? If access ends with the subscription, eight years of her work could be out of reach just when she needs it.
Tomorrow, someone she has cared for for years will sit across from her. She needs to remember what they have already tried and what comes next. She is ready to leave the software. She still needs the history they built together.
We believe changing tools should not make that history less useful. Patients should be able to obtain and share their information. Providers should be able to maintain and move the records they are responsible for.
Local First Health is an early-stage initiative. Our mission is to help more local-first health apps get built around that belief. No clinical product is available through LFH.
Where the record lives
Local-first software keeps a usable copy of data on your device and supports work without a constant internet connection. Sharing records between different apps needs compatible software.
All three approaches are still used today. These are simplified examples: some cloud apps work offline too, and sharing features vary by app.
Pre-cloud era
Records stay on a clinic computer. You can use them without internet, but moving them to another device takes a separate step.
Cloud era
Records are kept on the software provider’s computers. You open them over the internet, so access depends on the service and your connection.
Local-first era
A working copy stays on your device. Essential work should continue offline, with updates shared when devices can connect.
What we want health apps to make possible
These are the qualities we want health apps to have. They are goals for software, not features LFH delivers today.
They draw on the seven local-first ideals from Ink & Switch and the responsibilities that come with health records. These twelve goals are LFH’s interpretation, independent of Ink & Switch.
Work offline
Essential recordkeeping should stay available when the internet goes down.
Keep your records
Patients and providers should be able to keep and move the records they need.
Keep using the software
Clinics should be able to keep using their software as their needs and providers change.
Standards you can check
Health apps should make their standards and evaluation results clear.
Privacy by design
People should know what leaves their device and who can access it.
Protect the record
Protection for devices, backups and shared records should be built in and explained.
Ready when needed
The record should be ready when a patient sits down.
Work together
Clinicians and patients should be able to share records with their source and date intact.
Copies that stay in step
Changes should travel between devices, with a clear way to resolve conflicting edits.
Usable local copies
A useful copy of the record should stay on the clinic’s own devices.
Open foundations
Open code and clear documentation should give others a foundation to build on.
Freedom to move
People should be able to retrieve their existing records without a fee and choose their next tool.
A person's history should outlast any app or company. The five proposed principles turn these beliefs into questions you can ask a software provider. Builders can also explore the wider local-first community.
What ownership means
Health data belongs to people, not platforms. A patient and the providers responsible for a record should be able to keep useful copies and decide how to share them.
Some systems already offer bulk exports. What comes out, what another tool can use, and what access remains after cancellation vary. Here are four questions worth asking:
- Can we keep a readable copy after our subscription ends?
- What is included in the export, and what is left out?
- Which parts can the next tool use, and what needs conversion or checking?
- Which essential tasks work without an internet connection, and with what limits?
Paying for software or support should never be a condition of retrieving existing records.
Moving records into another system may need additional work. That work is different from getting your existing records back.
Where LFH stands
LFH grew out of experience working in teams building health record systems since 2016. Read the background.
This is an early-stage initiative that develops as time allows. No clinical product or foundation codebase is available through LFH. See the current stage.
Local-first reduces dependence on central services. It does not make privacy or security automatic. Each implementation must explain how it protects devices, backups and shared records. These principles are not a HIPAA compliance assessment.
Further reading
LFH is part of a wider conversation about software people can keep and use. These sources discuss the ideas; neither is an endorsement of LFH.
“Local-first software: You own your data, in spite of the cloud”
The essay that named the seven ideals.
“The Cloud Is a Prison. Can the Local-First Software Movement Set Us Free?”
The local-first movement, outside health. It does not cover LFH.
If you believe this too
Picture the choice we want that doctor to have. Before deciding whether to stay, she has checked what she can keep reading, what the next system can use, and what needs more work. Retrieving her existing records carries no fee.
She decides to stay. Staying is now a choice.
If these ideas matter to your work, share a workflow problem, question or perspective. We have limited capacity and may be slow to respond.