|1:30 Pm Eastern||Agenda Check||Rob H|
FHIR-27796 Incorporate relatedArtifact into ConceptMap and/or extend workflow-relatedArtifact to allow it on ConceptMap. This ticket is resolved, change required. Vocab tracker call attendees would like to discuss.
The base issue is that the datatype allows references in both directions. There is no ability to control which resource types make sense for a resource type. Difficult to control mustSupport, etc.
This was originally just in the Decision Support resources, and it is popping up all over the place. Its not clear whether that is a good idea.
The Decision Support workgroup has primary control. M&M has brought some issues to their attention.
Has Vocabulary looked at this and evaluated it from an 80% rule perspective - all the resources make sense.
Will 80% of implementers support the datatype for ConceptMap?
Since this was added in the extension space, it is less of a concern, and might not be of any concern. However, if you use the extension, you have to support the full extension, you can't pick and choose. This is more of an issue for CDS, M&M is working with CDS on this.
Nothing more to do.
This ticket has been applied.
|Terminology Expectations Alignment|
The material presented at the co-chair webinar was reviewed. Attached to the minutes below. (see section on FHIR Updates -Development and Balloting Roadmap
2022 04 07 - Co-Chair Webinar.pdf (note this is the ppt that was shared at the co-chair webinar, and this session covered the topics and identified where changes need to be communicated - the material had not been vetted by vocab or TSMG)
Final thoughts/Action items:
TK: do we have a final decision with making the pending code system tab real or not?
RM: we need a restatement of what we agreed to, voted on by FMG and TSMG. Jess will add this to the TSMG call Q4 Thursday.