Validate FHIR R4 resources and Bundles for US Core conformance.
npx skills add https://github.com/maziyarpanahi/openmed --skill validating-us-core
Please help me install this Agent Skill. Skill: validating-us-core Source: https://github.com/maziyarpanahi/openmed/tree/main/skills/validating-us-core Command: npx skills add https://github.com/maziyarpanahi/openmed --skill validating-us-core
This Skill identifies and resolves US Core and USCDI conformance issues that can cause OpenMed-produced FHIR resources and Bundles to be rejected by EHR systems such as Epic and Cerner.
Use the validating-us-core skill to validate the assembled synthetic or de-identified FHIR Bundle against a pinned US Core implementation guide and summarize the issues that must be fixed.
High-intent search queries and answers about installing and using this skill.
FHIR resources are validated against US Core profiles by running the HL7 validator_cli.jar or validator.fhir.org with the appropriate US Core implementation guide packages and terminology server access to detect conformance gaps. The results are converted into structured OperationOutcome responses for resolution.
US Core must-support validation checks FHIR R4 resources for required meta.profile declarations, must-support elements, required statuses, coded values, categories, subjects, and UCUM units to ensure USCDI conformance before EHR ingestion.
Yes, the HL7 validator_cli.jar validates assembled FHIR Bundles against pinned US Core implementation guides to identify and resolve conformance issues that would cause rejection by EHR systems like Epic and Cerner.
Yes, terminology server access is required alongside the HL7 validator_cli.jar and US Core implementation guide packages to validate coded values and terminology bindings within FHIR resources for USCDI conformance.
FHIR Bundles fail must-support checks during US Core validation when meta.profile declarations are missing, required statuses are absent, coded values do not match terminology bindings, or vital-sign profiles lack UCUM units. Structured OperationOutcome findings pinpoint these exact conformance gaps.
The best way to resolve OperationOutcome errors from FHIR US Core validation is to parse the structured findings, correct the identified must-support and profile declaration gaps in the exporter, and re-run the validator against the pinned US Core release to confirm EHR submission readiness.
rnavarychImplement HL7 FHIR R4 resource management and RESTful API interactions.
aks-buildsParse and validate FHIR R4/R5 resources using Python libraries.
maziyarpanahiFetch clinical narratives from FHIR R4 resources with Bundle pagination.
1Mangesh1Validate FHIR R5 resources, HL7 v2 messages, and CDA documents.
