Blog
Field notes on healthcare data import
Working posts on mapping messy partner files to clean, coded, FHIR-shaped output — written by the team that builds the cascade. Practical, accurate, and honest about the compliance trade-offs.
- FHIRpatient demographics
CSV to FHIR: Mapping Patient Demographics Step by Step
Walk a messy partner CSV through the patient_demographics template and out the other side as a clean FHIR Patient resource — name, gender, birthDate, and identifier — without hand-writing a mapping file.
8 min readRead post → - HIPAAschema-only
HIPAA-Safe CSV Import: What Schema-Only Mode Actually Does
Schema-only mode sends only column headers and up to three short sample rows — never the full file. Here is precisely what leaves your system, why so little leaving you usually means no DPA, and how the compliance posture changes when you switch to full-data mode.
7 min readRead post → - LOINClab results
LOINC Codes in CSV: Resolving Free-Text Lab Values
Lab CSVs almost never arrive with LOINC codes — they arrive as free text like "Hgb" or "Glukose nüchtern". Here is how the cascade and the loinc validator turn that free text into a coded lab result you can trust.
8 min readRead post →