FHIR Validation on Azure: Default Settings and Pitfalls
FHIR Validation on Azure - Darren Devitt Darren Devitt Microsoft
Microsoft Azure provides FHIR validation services for data that may not conform to standards.
Summary
Microsoft Azure's FHIR servers are forgiving regarding non-conforming data because resource creation and update validation is off by default. However, some validation still occurs for specific elements, and enabling profile validation requires explicit header settings, necessitating caution about potential operational surprises.
Key Players
Details
Microsoft Azure’s FHIR servers allow non-conforming data when creating or updating resources because the validation feature is switched off by default. This can lead to unexpected data acceptance. However, validation does not entirely cease; for instance, sending an Encounter without a subject will still correctly trigger an OperationOutcome response. More critically, profile validation is completely disabled unless the user explicitly adds and sets the `x-ms-profile-validation` header to true in the request. If a project has been running for months without this header, enabling it suddenly could reveal numerous non-conforming resources that were previously unnoticed, potentially causing significant operational issues. Therefore, thorough testing of this validation header is strongly advised before rolling out changes to production environments.
Technology Note
FHIR（Fast Healthcare Interoperability Resources）は医療データ交換の国際標準。このエントリの関連技術: FHIR
Original content copyright by respective publishers