Sharing Valuesets, Codes, and Maps (SVCM), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 1.5.2-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.SVCM/ and changes regularly. See the Directory of published versions

Sharing Valuesets, Codes, and Maps (SVCM)

Official URL: https://profiles.ihe.net/ITI/SVCM/ImplementationGuide/ihe.iti.svcm				Version: 1.5.2-current
Active as of 2024-05-06				Computable Name: IHE_ITI_SVCM

The Sharing Valuesets, Codes, and Maps (SVCM) Profile defines a lightweight interface through which healthcare systems may retrieve centrally managed uniform nomenclature and mappings between code systems based on the HL7 Fast Healthcare Interoperability Resources (FHIR) specification.

Organization of This Guide

This guide is organized into following sections:

• Volume 1: Profiles
  • Overview
  • Actors and Transactions
  • Actor Options
  • Actor Required Groupings
  • Overview
  • Security Considerations
  • Cross Profile Considerations
• Volume 2: Transaction Detail
  • Query Value Set [ITI-95]
  • Query Code System [ITI-96]
  • Expand Value Set [ITI-97]
  • Lookup Code [ITI-98]
  • Validate Code [ITI-99]
  • Query Concept Map [ITI-100]
  • Translate Code [ITI-101]
• Other:
  • Changes to Other IHE Specifications
  • Download and Analysis
  • Test Plan

Click on any of the links above, navigate the contents using the Table of Contents, or if you are looking for a specific artifact, see the index of Artifacts defined as part of this implementation guide.

Conformance Expectations

IHE uses the normative words Shall, Should, and May according to standards conventions.

Must Support

The use of mustSupport in StructureDefinition profiles equivalent to the IHE use of R2 as defined in Appendix Z.

mustSupport of true - only has a meaning on items that are minimal cardinality of zero (0), and applies only to the source actor populating the data. The source actor shall populate the elements marked with MustSupport, if the concept is supported by the actor, a value exists, and security and consent rules permit. The consuming actors should handle these elements being populated or being absent/empty. Note that sometimes mustSupport will appear on elements with a minimal cardinality greater than zero (0), this is due to inheritance from a less constrained profile.