FHIR Provenance Resource: Server-Side Responsibility for External Application Data Validation
Ownership of FHIR's Provenance Resource - Darren Devitt Darren Devitt
Summary
While FHIR standards dictate that the initiating application must provide a Provenance resource, the managing FHIR server must perform deeper validation—including source authentication and structural integrity checks—to ensure data quality.
Details
The FHIR standard requires applications creating or updating resources (e.g., Observation) to include a Provenance resource documenting their role in the transaction bundle. This is considered best practice for maintaining data lineage. However, relying solely on external applications to correctly populate this metadata is insufficient for robust real-world systems. To ensure data quality and consistency, a FHIR server or façade layer must implement several verification steps: 1. Verify the source of incoming data using authentication mechanisms (client ID, token). 2. Confirm the presence of a Provenance resource in the incoming Bundle. 3. Validate that the `Provenance.agent.who` matches the authenticated source. 4. Optionally, add extra agents to document the source from the server's perspective. 5. Verify that `Provenance.target` correctly references all resources within the Bundle. Furthermore, advanced servers can enhance traceability by updating the Provenance after processing—for instance, adding a version number reference to the target element. This highlights the necessity of proactive data governance beyond merely accepting application-provided metadata.
Technology Note
FHIR(Fast Healthcare Interoperability Resources)は医療データ交換の国際標準。このエントリの関連技術: FHIR
Original content copyright by respective publishers