How fhir/fhir-test-cases works
fhir-test-cases is a static corpus of FHIR test resources distributed for implementations to use in their own test regimes. The principal workflow is for an implementation or test harness to obtain the corpus through Maven or a release download, then select versioned examples and focused suites for its validation needs. The repository also preserves specialized cases for cross-version validation, CDA, UCUM, and formats such as GraphQL and FHIRPath. The README and tree establish these capabilities; sampled Java and JavaScript excerpts do not establish how external harnesses consume them, so those connections are not inferred.
Main entry points: r3 R3 Cases · r4 R4 Cases · r4b R4B Cases · r5 R5 Cases
Components 18
Focused Suites
- FHIRPath Cases
r4/fhirpath - GraphQL Cases
r4/graphql - Liquid Cases
r4/liquid - Patch Cases
r4/patch - Narrative Cases
r4b/narrative - Snapshot Cases
r4b/snapshot-generation
Specialized Cases
- Cross-Version Validation
validator - CDA Cases
cda - UCUM Source
ucum
Corpus Access
- Maven Artifact
- Release Download
Other components
- FHIR Implementer
- Test Harness
Connections 18
- FHIR Implementer → Maven Artifact: obtains artifact
- FHIR Implementer → Release Download: downloads corpus
- Maven Artifact → Test Harness: provides corpus
- Release Download → Test Harness: provides corpus
- Test Harness → R3 Cases: selects cases
- Test Harness → R4 Cases: selects cases
- Test Harness → R4B Cases: selects cases
- Test Harness → R5 Cases: selects cases
- Test Harness → R6 Cases: selects cases
- Test Harness → FHIRPath Cases: selects cases
- Test Harness → GraphQL Cases: selects cases
- Test Harness → Liquid Cases: selects cases
- Test Harness → Patch Cases: selects cases
- Test Harness → Narrative Cases: selects cases
- Test Harness → Snapshot Cases: selects cases
- Test Harness → Cross-Version Validation: selects cases
- Test Harness → CDA Cases: selects cases
- Test Harness → UCUM Source: selects source