FHIR template guides, multilingual matching, the schema-only contract, and the lessons learned shipping a healthcare-aware mapper. Written by the team that runs the cascade.
One number, three names, three languages, and a check digit. How AdaptivMapr resolves the Swiss social security number across CH-DE, CH-FR, and CH-IT data sources.
Read →The default mode of AdaptivMapr never sees a full row of patient data. Here is what does leave the browser, what does not, and why the legal review takes an afternoon.
Read →Swiss healthcare data arrives in three languages on the same file. Here is how the cascade resolves "Vorname", "Prenom", and "Nome" to the same field.
Read →Why generic CSV importers struggle with PHI, and how schema-only mode plus BAA inheritance change the integration calculus.
Read →A practical look at validating LOINC codes in a lab-result import, with examples drawn from the AdaptivMapr lab_result_catalog template.
Read →How AdaptivMapr maps messy patient roster spreadsheets to a FHIR Patient resource, including identifiers, name parts, and contact points.
Read →