Writing brief. This essay has been assigned but the manuscript is not yet written or approved. What follows is the commissioning brief: its question, outline, evidence instructions, and review requirements.
Central question
How can systems exchange meaning across different vocabularies?
Reader promise
Identifiers and mappings help knowledge move between applications. The reader will finish knowing what a mapping can promise, what it cannot, and what to ask of a terminology service before trusting it.
Required development
- Follow a single synthetic observation between systems. Invent one finding from a nuclear medicine report (for example, a focus of increased tracer uptake at a stated site) and trace it from the reading workstation into a departmental system, a hospital record, a registry, and a research dataset, noting at each hop which parts of the meaning are carried by a code, which by free text, and which are dropped.
- Explain CodeSystem, ValueSet, and ConceptMap as HL7 FHIR defines them: a code system defines codes and their meanings; a value set selects codes for a use; a concept map states relationships between codes in specified systems. Show how the three differ in purpose and how each is versioned.
- Compare equivalence with broader and narrower mappings. Use the synthetic observation to show when a target code says more, says less, or says something different, and why the direction of a map matters.
- Show what terminology services do: lookup, expansion of a value set, validation of a code, translation across a map, and subsumption testing. State for each operation what it depends on (edition, version, permissions) and what it does not establish.
Evidence and review
Evidence to obtain: the HL7 FHIR R5 specification pages for CodeSystem, ValueSet, ConceptMap, and the terminology service operations, cited with the release pinned; the SNOMED CT logical model and the current documentation of its relationship types; at least one published description of a real cross-vocabulary mapping effort with its reported error or coverage rates, for use as a documented case rather than an assumption.
All codes shown in the figure or prose must either be verified against the named release or be labeled as local teaching identifiers. The mapping table figure must show source, target, direction, relation, version, and scope.
Review concern: a reader may conclude that a mapping or an identifier guarantees preserved meaning. The manuscript must state that transport of a code does not demonstrate shared interpretation, and that NucLex has no live terminology endpoint.
Planned internal links
SNOMED CT, FHIR, Concept map, Terminology server, Code system, Value set, Identifier, and FHIR terminology resources for the longer treatment. Link at the point of use.
Review requirements
Source check against version-specific HL7 and SNOMED International documentation. Domain review by an informatician familiar with FHIR terminology services. Editorial check that every displayed code is either verified or visibly local.