Releases

Release Notes — v0.1.0

Key information about the initial draft release of the Li Xinyang FHIR-Native Interoperability Framework.

What's Included

• Initial FHIR R4 formalization of the interoperability and data-quality methodology.
• 35 canonical FHIR R4 resource profiles with generated snapshots.
• 11 registered extensions for source identity, mapping provenance, validation stages, quality metrics, and tamper-evident lineage.
• 9 normalized source logical models for representative HL7 v2 segments and C-CDA entries.
• Terminology artifacts for six data-quality metrics and mapping/validation metadata — 7 CodeSystems, 7 ValueSets, 11 ConceptMaps, and 12 StructureMaps with readable FML sources.
• 1 generated ImplementationGuide, 1 CapabilityStatement, 2 draft OperationDefinitions, and 2 SearchParameters.
• 17 standalone synthetic examples and 1 canonical exchange Bundle.
• Deterministic integrity checks, offline R4 validation, artifact inventory, traceability matrix, and FHIR NPM package assembly.
• 116 total FHIR JSON resources including 55 StructureDefinitions with generated snapshots.

Build & Validation

• SUSHI 3.20.0 compilation with snapshot generation completed with no errors.
• Deterministic package-integrity checks passed with no errors or warnings.
• Offline R4 validation of 61 non-StructureDefinition resources yielded no fatal, error, or warning findings.
• Build pipeline: SUSHI compilation → assembly → inventory → integrity check → offline validation.

Known Limitations

• This is a draft and experimental release — not for production use.
• The canonical base is https://example.org/fhir/li-xinyang-interop-r4; replace with a controlled, durable domain before publication.
• NDC→RxNorm, ICD-9-CM→ICD-10-CM, and local-code crosswalks are intentionally empty governance templates.
• HL7 v2 and C-CDA StructureMaps begin from normalized logical inputs after transport parsing and document/segment extraction.
• TF-IDF matching, live $validate-code, Merkle-tree storage, and federated-query runtime components are method and interface contracts, not completed services.
• All examples are synthetic and all performance figures remain targets or concept-of-concept values.
• Package has not been run through the official HL7 Java validator and does not replace a live terminology-server pass, licensed terminology review, institution-specific conformance testing, security testing, clinical-safety review, or production acceptance testing.