Lang2FHIRFHIR ArtifactsFHIR2OMOP
Lang2FHIR batch processing, patient matching, and versioned FHIR profiles
Lang2FHIR
patient_referenceis deprecated for multi-resource requests; useprimary_patientonPOST /lang2fhir/create/multiorPOST /lang2fhir/document/multiinstead.- Asynchronous batch processing lets you submit work, poll its progress, and retrieve each item’s result when it is ready. Start with
POST /lang2fhir/batch. - Primary-patient matching lets multi-resource extraction use a patient identifier, name, birth date, or gender to associate clinical resources with the right patient. Set
primary_patientonPOST /lang2fhir/create/multiorPOST /lang2fhir/document/multi. - Resource review optionally removes unsupported codings and quarantines resources that cannot be repaired, so you can inspect
flaggedandremediatedoutput before using it. Configureresource_reviewon the multi-resource endpoints. - Additional document and resource support accepts RTF and XML/C-CDA on dedicated instances and adds
familymemberhistory,medicationadministration, andmedicationstatementfor single-resource requests. Start withPOST /lang2fhir/document.
FHIR Artifacts
- Pinned profiles and versions cannot be deleted while a guide package depends on them; that request now returns
409. Remove the dependency before callingDELETE /fhir/profiles/{id}orDELETE /fhir/profiles/{id}/versions/{version}. - Custom profile version history preserves profile revisions so clients can resolve a specific
url|versioninstead of always using the latest definition. Start withGET /fhir/profiles/{id}/versions. - Versioned implementation-guide packages pin exact profile versions for reproducible guide releases. Create a release with
POST /fhir/implementation-guides/{name}/versions; deleting a guide also removes its package versions.
FHIR2OMOP
- Medication and Observation mapping behavior changes:
MedicationRequestnow usesdrug_type_concept_id32838, and coded Observations route by their OMOP concept domain. Review downstream expectations forPOST /fhir2omop/create. - Broader OMOP table coverage adds provider, care site, location, death, and observation-period data, giving downstream analytics more of the care context. Start with
POST /fhir2omop/create. - Richer medication and diagnostic output adds drug end dates, refills, supply, route, and lot details, plus diagnostics for references that cannot be linked. OID-form coding systems are also accepted by the converter.