Local‑first model
CareFlow Kids and CareView Family follow a local‑first architecture.
This means that medical data is primarily stored locally on the device rather than in a central online database.
The goal of this model is to give clinicians and families direct control over medical information while reducing unnecessary exposure of sensitive health data.
Where data is stored
Patient data is stored inside a .pemr bundle.
A .pemr bundle typically contains:
- the structured medical database
- sick and well visit records
- growth measurements
- attached medical documents
The bundle can be opened by:
- CareFlow Kids (doctor app)
- CareView Family (patient viewer)
Because the record lives in the bundle itself, it can be moved safely between devices without relying on a permanent central server.
No permanent central database
Unlike many electronic medical record systems, CareFlow Kids does not rely on a permanent centralized patient database.
Instead:
- clinicians open or import a patient bundle when needed
- the consultation is recorded locally
- the updated bundle can then be exported and shared privately
This approach doesn't rely on medical data stored online. Parents are the primary owner and holders of their kids' medical data.
Portable patient record
The .pemr bundle acts as a portable medical record.
This means the patient's record can move between:
- the clinician's device
- the family's device
- other clinicians when required
The same bundle always contains the current cumulative medical record.
Benefits of the local‑first approach
This architecture provides several advantages:
- greater privacy — fewer centralized databases storing health data
- patient portability — the record travels with the patient
- offline capability — records can be accessed without internet access
- simpler data ownership — the bundle itself represents the medical file
Responsibilities when using local‑first records
Because the record is stored in a portable file, users should take reasonable precautions.
Clinicians and families should:
- keep
.pemrfiles in secure locations - share bundles only with trusted recipients
- maintain backup copies when appropriate
These simple practices help preserve both privacy and data integrity.