Coming Fall 2023:
Announcing Single Sign-On for HL7.org, Confluence, and Jira.
Log in
Skip to sidebar
Skip to main content
Linked Applications
Loading...
Confluence
Spaces
People
Glossaries
Hit enter to search
Help
Online Help
Keyboard Shortcuts
Feed Builder
What’s new
Available Gadgets
About Confluence
Log in
Terminology Infrastructure
Pages
Space shortcuts
HL7 Main Page
HL7 Terminology Authority (HTA) Page
HL7 Vocabulary Work Group
HL7 Work Groups & Projects
Vocab Meetings and Calls Details
Glossaries
Jira reports
Next WGM (Sep 2023) Agenda
Page tree
Browse pages
Configure
Space tools
A
t
tachments (3)
Page History
Glossary
Resolved comments
Page Information
View in Hierarchy
View Source
Export to PDF
Export to Word
Export to PDF
Copy Page Tree
Hide Inline Comments
Pages
…
Terminology Infrastructure Work Group (formerly Vocabulary Work Group)
Vocabulary Work Group Policy Statements
Policy on Maintenance of External Code System Identifiers (URIs)
Internal Code System Identifier Management - Task Force
Jira links
Viewtracker
Workflow process for use of internal code system identifiers in FHIR and beyond
Created by
Rob McClure
, last modified by
Carmela A. Couderc
on
Oct 01, 2021
No labels
1 Comment
Mark Kramer
Is it intended that there is always a one-to-one relationship between CodeSystem and NamingSystem?
Permalink
Apr 08, 2021
Overview
Content Tools
Apps
{"serverDuration": 164, "requestCorrelationId": "3ae6e69ee4e21ae0"}
1 Comment
Mark Kramer
Is it intended that there is always a one-to-one relationship between CodeSystem and NamingSystem?