FHIR / Bulk FHIR
Read Patient, Observation, Procedure, Condition, DiagnosticReport, FamilyMemberHistory, and related resources from the health system's governed API or export process.
Integration overview
No-PHI pilot first. Real patient data only after governance.
The Closr public MVP runs on synthetic patients so health-system buyers can evaluate the workflow without PHI. The first paid pilot should use synthetic or properly de-identified inputs and produce the data map, security asks, and BAA path needed for a later PHI pilot.
FHIR means Fast Healthcare Interoperability Resources: the API-oriented healthcare data standard used to exchange resources such as patients, observations, procedures, conditions, and diagnostic reports.
Interface or data warehouse extract
Load an approved daily or weekly extract from Epic, Oracle Health, Health Catalyst, Snowflake, or the organization's analytics warehouse.
No-PHI readiness pack
For the first paid pilot, use synthetic records, aggregate workflow counts, schema samples, or properly de-identified examples. Do not include names, MRNs, dates of birth, or EHR exports.
Production data set after BAA
- Patient identity, demographics, empanelment, PCP, and department
- Screening procedures and results: mammography, FIT/FOBT, stool DNA, colonoscopy, Pap/HPV, and LDCT
- Risk factors: tobacco history, pack-years, BMI, family cancer history, genetic findings where governed, prior adenomas, and COPD
- Orders, outside completions, patient-reported evidence, and manual reconciliation events
Controls before PHI
- No PHI in the first readiness pilot
- BAA-covered hosting before PHI
- OIDC/SSO with tenant-scoped roles
- Encryption in transit and at rest
- Append-only audit log for actions and ruleset versions
- PHI-safe logging and retention policy
- Clinical governance review for guideline and calculator changes
30-day no-PHI readiness pilot
The first pilot should start with breast, colorectal, lung, and cervical screening pathways. The health system provides workflow context, aggregate counts, schema samples, and synthetic or properly de-identified examples. Closr configures the workbench and delivers a PHI-pilot readiness memo covering data fields, security gates, success metrics, and expected ROI.