Attendance can be found here
Co-Chair and Key Participant information can be found on the Agenda found here
|3:30||Value Set Definition Project||Rob McClure|
An expansion is a group of metadata associated with the collection, then there are the members of the collection itself. Every code system has concept identifiers and most record these as codes. they may also have descriptions (or display names), some have properties and relationships associated with the concept. The user community has indicated that they would sometimes like selected additional data components in the value set expansion. Sjpecific component candidates are whether the item is active or not. There is a need to clearly define in a standardised way, what the extra components might be and how these should be managed.
The list in the VSD set project page identifes specific requirements Value Set Definition (VSD) Project documents Metadata about the expansion.
It was agreed to
There are also difficulties and requirements to know the service used to create the expansion and to be able to determine the source of information. The receiver cannot necessarilly assume this information and may need to know this to process data correclty. If these things are not known by the service which generates the expansion then the service has to do so before it is usble by a third party. This could include:
though the use case is understood the effort to do this does not seem to be worth the return and at the moment it was decided not to include this functionality.
Date / Time of expansion
The Expansion Profile CononicalID must cover the 90% case is code system, code system version, code and display name.
It was suggested that an example be created and included in the documentation.
- Include an example of expansion profile and the result of that profile to clarify the use case - Rob McClure