Three architectural principles.
Every design and engineering decision is judged against them.
Patient-centric, inclusive design.
Every surface meets the patient where they are. SHIRLe ingests health data from where patients already keep it — Apple Health, Dexcom, Fitbit, the back of a prescription bottle, a screenshot of a wearable’s weekly chart — without requiring API contracts or technical literacy.
The HealthDigits AVS scanner, deployable today, is the first surface where this principle becomes visible: photograph a printed After Visit Summary, and the pipeline recognizes what it is and files it correctly.
If you can take a screenshot,
you can contribute your data.
Secure, with the patient in control.
Consent is a first-class architectural object. Owned by the patient. Granular. Revocable. Portable across vendors. Durable as patient capacity changes. Modeled as a FHIR Consent resource that the patient can read, audit, and edit.
The patient is not a record in our system — the patient controls the system. As agentic AI moves from suggestion to action, the consent layer beneath it must be patient-controlled. The patient owns consent. Everything else follows.
Interoperable with the ecosystem.
SHIRLe is FHIR R4-native and built to work with the healthcare infrastructure that already exists. A multi-pass pipeline will convert patient-supplied data — photographs, screenshots, PDFs, device readings — into FHIR observations against the patient’s own longitudinal record.
SMART on FHIR provider integration is scaffolded from day one. Initial launch focuses on consumer-direct ingestion; provider-side authorization follows. The platform does not ask the world to change to accommodate it. It meets the world where it is.
Data-fabric components launch with the CMS ACCESS Model rollout in July 2026 through sister platform IntelaCare. That is SHIRLe’s first federal production deployment.