What shipped

• TIFF uploads now require a dedicated instance. Lang2FHIR document endpoints apply the same availability constraint that already covers RTF and XML/C-CDA: POST /lang2fhir/document and POST /lang2fhir/document/multi return 403 for TIFF content on instances that are not dedicated. PDF, PNG, and JPEG uploads are unchanged.

Lang2FHIR

• patient_reference is deprecated for multi-resource requests; use primary_patient on POST /lang2fhir/create/multi or POST /lang2fhir/document/multi instead.
• 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_patient on POST /lang2fhir/create/multi or POST /lang2fhir/document/multi.
• Resource review optionally removes unsupported codings and quarantines resources that cannot be repaired, so you can inspect flagged and remediated output before using it. Configure resource_review on the multi-resource endpoints.
• Additional document and resource support accepts RTF and XML/C-CDA on dedicated instances and adds familymemberhistory, medicationadministration, and medicationstatement for single-resource requests. Start with POST /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 calling DELETE /fhir/profiles/{id} or DELETE /fhir/profiles/{id}/versions/{version}.
• Custom profile version history preserves profile revisions so clients can resolve a specific url|version instead of always using the latest definition. Start with GET /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: MedicationRequest now uses drug_type_concept_id 32838, and coded Observations route by their OMOP concept domain. Review downstream expectations for POST /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.

The Phenoml changelog is now live. Follow this page for developer-focused updates to the platform and API.