# Methodology-to-Artifact Traceability Matrix

**Package:** `li-xinyang-interop-r4#0.1.0`  
**Source basis:** the two supplied July 2026 methodology narratives  
**Status:** draft technical formalization; not production-deployment evidence

| Component | Methodology assertion | Implemented artifacts | Status and boundary |
|---|---|---|---|
| **Canonical FHIR R4 data model**<br>Line1 Framework §2.1 (p.3); Mainline Technical Methodology Brief (p.1) | Approximately 35 core clinical resource types constrained by mandatory fields, cardinalities, and terminology bindings. | 35 resource profiles; 55 total StructureDefinitions<br><code>input/fsh/04_profiles_admin.fsh; input/fsh/05_profiles_clinical.fsh; input/fsh/06_profiles_governance.fsh; fsh-generated/resources/StructureDefinition-*.json</code> | Implemented as draft specification. Exactly 35 profiles were selected to make the approximate scope computable; production cardinalities require site review. |
| **Strict at core, flexible at edges**<br>Line1 Framework §2.1 (p.3); Mainline p.1 | Core exchange primitives are mandatory while institution-specific content uses a registered extension catalog. | HITCStrictCoreMetadata RuleSet; 11 extensions<br><code>input/fsh/01_invariants_rulesets.fsh; input/fsh/03_extensions.fsh</code> | Implemented as draft specification. The package does not close all profiles to external extensions; governance policy remains required. |
| **HL7 v2 structural mapping**<br>Line1 Framework §2.2 (p.3), architecture p.5 | Declarative mappings for ADT/ORU/SIU/MDM/ORM-related segments such as PID, OBX, OBR. | 8 logical models; 7 HL7 v2 StructureMaps and FML files<br><code>input/fsh/07_logical_models.fsh; input/resources/StructureMap-v2-*.json; input/maps/v2-*.map</code> | Representative computable mapping rules. A source adapter must parse ER7 messages, repetitions, local tables, and Z-segments into the logical inputs. |
| **C-CDA structural mapping**<br>Line1 Framework §2.2 (p.3); Mainline p.1 | XPath/template-based extraction of medications, problems, allergies, procedures, and discharge medications. | C-CDA logical entry model; 5 C-CDA StructureMaps and FML files<br><code>fsh-generated/resources/StructureDefinition-HITCCCDAEntry.json; input/resources/StructureMap-ccda-*.json; input/maps/ccda-*.map</code> | Representative computable mapping rules. Raw XML/XPath extraction precedes these maps and is not implemented as a FHIR StructureMap. |
| **Terminology bridge**<br>Line1 Framework §2.3 (p.3); Mainline p.1 | Exact lookup, TF-IDF fuzzy matching, FHIR validate-code, confidence threshold, and human review. | 11 ConceptMaps; mapping strategy ValueSet; confidence/reviewer/original-code extensions<br><code>input/resources/ConceptMap-*.json; input/fsh/02_terminology.fsh; input/fsh/03_extensions.fsh</code> | Interface and provenance contract implemented. The TF-IDF algorithm and live terminology-service calls are not runtime implementations in this package. |
| **Governed external crosswalks**<br>Line1 Framework §2.3 (p.3) | Bridge across ICD, SNOMED CT, LOINC, RxNorm, NDC and local codes. | Five empty governed ConceptMap templates; supported-terminology CodeSystem<br><code>input/resources/ConceptMap-*-template.json; fsh-generated/resources/CodeSystem-hitc-supported-terminology.json</code> | Governance templates implemented. No licensed, release-sensitive, or institution-specific mappings are fabricated or redistributed. |
| **Unit and temporal normalization**<br>Line1 Framework §2.2 (p.3), architecture p.5 | Normalize units to UCUM and temporal values to ISO 8601-compatible FHIR datatypes. | Laboratory invariant requiring UCUM; typed date/dateTime logical fields; transformation activity codes<br><code>input/fsh/01_invariants_rulesets.fsh; input/fsh/05_profiles_clinical.fsh; input/fsh/07_logical_models.fsh; input/fsh/02_terminology.fsh</code> | Conformance rules implemented. Conversion formulas and source-specific parsing rules require an implementation. |
| **Composable validation pipeline**<br>Line1 Framework §2.4 (p.3); Mainline p.1–2 | R-SCH, R-REF, R-TERM, followed by a quality-metrics collector. | Validation-stage CodeSystem/ValueSet; validation extension; validate-exchange OperationDefinition; build checks<br><code>input/fsh/02_terminology.fsh; input/fsh/03_extensions.fsh; input/resources/OperationDefinition-validate-exchange.json; scripts/check_package.py</code> | Conformance contract and package checks implemented. Operational reference and terminology validation still require runtime services and site policy. |
| **Inline quality metrics**<br>Line1 Framework §2.4 and §3 (pp.3–4); Mainline p.1 | FFR, CSC, RIR, TC, MSR and TCR are emitted as FHIR Observations in the exchange path. | QualityMetricObservation profile; quality CodeSystem/ValueSet; numerator/denominator extensions; six examples<br><code>input/fsh/02_terminology.fsh; input/fsh/05_profiles_clinical.fsh; input/fsh/03_extensions.fsh; input/fsh/11_examples.fsh</code> | Implemented as profiles and synthetic examples. Example percentages are synthetic and are not measured production outcomes. |
| **Resource-level provenance**<br>Line1 Framework §2.5 (p.3); architecture p.5 | Each transaction records targets, source, steps, timestamps, and agents as FHIR Provenance. | Canonical Provenance profile; Provenance example; mapping and transformation extensions<br><code>input/fsh/06_profiles_governance.fsh; input/fsh/11_examples.fsh; fsh-generated/resources/Provenance-ExampleMappingProvenance.json</code> | Implemented as computable lineage contract. Append-only persistence and cross-organizational linkage are implementation responsibilities. |
| **Merkle tamper evidence**<br>Line1 Framework §2.5 (p.3); prior-art comparison p.7 | Append-only provenance records are anchored with Merkle-tree tamper-evident hashing. | Merkle-root extension and Provenance example<br><code>input/fsh/03_extensions.fsh; input/fsh/11_examples.fsh</code> | Data contract implemented. No durable Merkle tree, signing service, key management, or ledger is claimed. |
| **Federated query workflow**<br>Line1 Framework §2.6 (p.3), architecture p.5; Mainline p.2 | Materialized views, query decomposition/fusion, patient matching, and adaptive caching support low-latency summaries. | federated-summary OperationDefinition; CapabilityStatement<br><code>input/resources/OperationDefinition-federated-summary.json; input/resources/CapabilityStatement-hitc-interop-server.json</code> | API/requirements contract implemented. Planner, matching model, views, cache and latency targets are not runtime implementations. |
| **Access gateway**<br>Line1 Framework architecture p.5 | SMART-on-FHIR authorization, rate limiting, and audit logging protect access. | CapabilityStatement security declaration; AuditEvent profile<br><code>input/resources/CapabilityStatement-hitc-interop-server.json; input/fsh/06_profiles_governance.fsh</code> | Requirements-level declaration. OAuth registration, scopes, consent policy, rate-limit values and audit retention are site-specific. |
| **FHIR package formalization**<br>Line1 Framework §2.1 (p.3); Mainline p.1 | Profiles and guide artifacts are machine-consumable and loadable by standards-compliant systems. | ImplementationGuide JSON; FHIR NPM package; package index; FSH sources<br><code>sushi-config.yaml; fsh-generated/resources/ImplementationGuide-li-xinyang-interop-r4.json; dist/li-xinyang-interop-r4-0.1.0.tgz</code> | Implemented and packaged. The example.org canonical must be replaced before public or operational publication. |
| **Validation targets and evidentiary status**<br>Line1 Framework §5 (p.6); Mainline Validation and Benchmark Targets (p.2) | Targets are based on synthetic resources, test corpora, simulation, or literature projections. | Synthetic examples; validation reports; limitations documentation<br><code>input/fsh/11_examples.fsh; VALIDATION_REPORT.md; OFFLINE_FHIR_VALIDATION_REPORT.md; METHODOLOGY_ASSUMPTIONS.md</code> | Caveats preserved. No completed production deployment, external adoption, or achieved benchmark is asserted. |
