How to Implement Data Conversion using Azure Health Data Service
Azure Health Data Service の $convert-data endpoint を利用する - Zenn
Summary
This article details the implementation process for data conversion using the $convert-data endpoint of Azure Health Data Services. It provides concrete API calling methods and sample code for converting non-FHIR data (e.g., HL7v2) into FHIR format.
Details
This technical guide explains how to achieve interoperability by utilizing the $convert-data endpoint within Azure Health Data Services (AHDS). The focus is specifically on the conversion process from standard electronic health record message formats, such as HL7v2, into FHIR (Fast Healthcare Interoperability Resources). Since AHDS natively supports only FHIR, DICOM, and MedTech formats for storage, this API must be used when ingesting other data types. The article provides a concrete example of converting an ADT message from HL7v2 to FHIR, referencing related resources like Azure Data Factory and GitHub converters. The implementation code is provided in C#, detailing the structure of the JSON payload required to call the `$convert-data` API (including fields like `inputData`, `inputDataType`, `templateCollectionReference`, and `rootTemplate`). This offers practical technical information for developers integrating the service into real systems. This method is highly relevant to improving standardization and interoperability in Japanese healthcare IT, as it enables the conversion of data acquired from diverse legacy systems or external sources into the unified FHIR format.
Original content copyright by respective publishers