Attendance can be found Here
Co-Chair and Key Participant information can be found on the Agenda found Here
Naming System is a tightly and narrowly defined resource that is still at Maturity Level 1. A curated namespace that issues unique symbols within that namespace for the identification of concepts, people, devices, etc. Represents a "System" used within the Identifier and Coding data types. Examples of use would be things like National Patient Identifiers.
Defines a specific code system or identifier system, so that it can be noted in a registry for other systems to find and understand an identifier.
Three 'kinds' of Naming System
In the Identifier datatype us the 'System' is referring to the the Namingsystem.
Summary of last quarter:
Currently Concept Map is only intended to represent the nature of concept equivalency. Some have raised that other relationships should be included.
Some have suggested that other relationships could be managed using supplements, but this could lead to a case
Code system supplements could only reference members within the code system that are being supplemented, and expand Concept Map to include other relation types and change the name to reflect that other relation types are permitted and update the definition accordingly
Put an invariant on Code System Supplement to constrain the resource to only reference items within the code system and supplement. You cannot create properties that reference other code systems.
Concept Map is intended to create associations between concepts from different code systems. Code System Supplement is intended to extend the available attributes/properties/relationships within ONE SINGLE code system. ←Do we redefine Code System Supplement as such?
- Update the Identifier data type 'System' element to explicitly reference 'Namingsytsem' as opposed to 'namespace' in the description AND definition as well as in descriptive text throughout the datatype.
In our effort to evaluate the maturity level of Namingsystem we need to clarify the intent of the resource with examples Peter Jordan