This page is part of the Sharing Valuesets, Codes, and Maps (SVCM) (v1.5.0: Trial Implementation) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

1:51. Sharing Valuesets, Codes, and Maps (SVCM)

Official URL: https://profiles.ihe.net/ITI/SVCM/ImplementationGuide/ihe.iti.svcm				Version: 1.5.0
Active as of 2022-10-21				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 four main 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]

• Test Plan

• Changes to Other Profiles

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.

Download

You can also download:

• this entire guide
• the definition resources in json, xml, ttl, or csv format, or
• the example resources in json, xml or ttl format.

The source code for this Implementation Guide can be found on https://github.com/IHE/ITI.SVCM

Cross Version Analysis

This is an R4 IG. None of the features it uses are changed from R4B, so it can be used as is with R4B systems. Packages for both R4 (ihe.iti.svcm.r4) and R4B (ihe.iti.svcm.r4b) are available.

Dependency Table

Package ihe.iti.balp#1.1.1

The Basic Audit Log Patterns (BALP) Implementation Guide is a Content Profile that defines some basic and reusable AuditEvent patterns. This includes basic audit log profiles for FHIR RESTful operations to be used when there is not a more specific audit event defined. A focus is enabling Privacy centric AuditEvent logs that hold well formed indication of the Patient when they are the subject of the activity being recorded in the log. Where a more specific audit event can be defined it should be derived off of these basic patterns. (built Fri, Oct 21, 2022 08:58-0500-05:00)

Dependencies

• Audit Event for Query Code System Transaction by the Terminology Consumer and Repository for Query derives from Basic AuditEvent for a successful Query
• Audit Event for Query Code System Transaction by the Terminology Consumer and Repository for Read derives from Basic AuditEvent for a successful Read
• Audit Event for Query Concept Map Transaction by the Terminology Consumer and Repository for Query derives from Basic AuditEvent for a successful Query
• Audit Event for Query Concept Map Transaction by the Terminology Consumer and Repository for Read derives from Basic AuditEvent for a successful Read
• Audit Event for Expand Value Set Transaction by the Terminology Consumer and Repository derives from Basic AuditEvent for a successful Read
• Audit Event for Query Value Set Transaction by the Terminology Consumer and Repository for Query derives from Basic AuditEvent for a successful Query
• Audit Event for Query Value Set Transaction by the Terminology Consumer and Repository for Read derives from Basic AuditEvent for a successful Read

Globals Table

No Global profiles found

IP Statements

• This publication includes IP from Audit Event ID. These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright © 2011 by the National Electrical Manufacturers Association.
• This publication includes IP from DICOM Controlled Terminology Definitions. These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright © 2011 by the National Electrical Manufacturers Association.