Spike: Ensure FHIR converter meets fhir spec

What needs to be done

We need to ensure that our FHIR conversion service generates FHIR bundles that are fully compliant with the current FHIR specification. This involves testing the generated FHIR bundles against the latest FHIR standards to identify and resolve any discrepancies.

Why it needs to be done

Ensuring compliance with the current FHIR specification is crucial for interoperability with other systems that rely on FHIR. Non-compliant bundles could lead to data exchange issues, errors in patient information handling, and overall system inefficiency. Compliance is necessary to maintain trust and functionality within the healthcare ecosystem.

Acceptance Criteria

The generated FHIR bundles must pass validation against the current FHIR specification.
Any discrepancies or non-compliance issues found during testing must be resolved.
A report detailing the testing process, results, and any changes made to achieve compliance.

Technical Notes

Review the current FHIR specification to understand all required elements and constraints.
Utilize available FHIR validation tools or libraries to automate the testing process.
Ensure that any updates made to achieve compliance do not introduce regressions in other parts of the service.
Testing should include different types of FHIR bundles (e.g., patient demographics, observations, etc.).

CDCgov / phdi