Working on a workflow solution for generating new OIDs for internal (UTG) code systems and value sets that are created
We have implemented a Confluence form for this which is at OID Generation
Note that we STILL do not have the finalized policy on Code System versioning. This is critical.
We have not yet fully tested the generation of the MIF
The generated MIF is rebuilt every time we have new content update (commit to the UTG Git SoT)
We REALLY need to schedule the testing and validation of this generated MIF
We need to clearly communicate the community of MIF consumers where and when and how they access the MIF
We need to clearly state that the release 1.0.0 is an initial release and has known content deficiencies
For the wide-scale UTG rollout we need to make sure we communicate to folks that use the MIF what they need to know
On initial examination, the generated MIF files look wrong in major ways ie less than half the size they should be, etc. Must review with Lloyd. MAJOR ISSUE: the MIF from 1.0.0 is identical in content (except for the timestamp for generation) with the UTG MIF from 1.0.18 - refer to Lloyd,
Governance Policy on Unification
Still waiting for Rob Hausam to put in his Pilot proposal to do the final unification of ObservationInterpretation.
Do we need any discussion of it on main Vocab WG call this week July 9? We will do the proposal as we think it should be done, look fro feedback, and hope for the best.
In work, we still need additional participation. Please vote!
For non-HL7 content, we need to define our precise process to work through the HTA recommendations.
Next call we should work on documenting the process for doing this
Rob M asked that we discuss the URLs issue especially wrt the CDC PHINVADS URLs
Specifically, we have ODH code systems added by Mary Kay last year and PHINVADS is the source of truth of the content for the military service rankings. This is a FHIR resource and a FHIR IG so needs the proper and correct canonical URL.
We have a bunch of these and we should have a policy to fix them
This an HTA/Vocab issue (HTA-5) that speaks to this
Note that when these were added we had ONLY the OIDs, and NO canonical URLs. Therefore they ALL carry the 'bogus' pro-forma generated URL two make the UTG pages build; these all need to be corrected
Other longer term items
tabled, out of time
Need to setup the list for the immediate items that must be addressed as soon as we go live
Editing of manifests
May be later; may be done manually for some time after go-live
Tasks are broken down by pre-last import, pre-initial release, post-initial release but pre-pilot, post-pilot, pre-largescale rollout, then R2 and beyond R2 thus it includes all of the longer term items
Publication and maintenance for the VSAC value sets which are actually HL7 V3 value sets which have historically been maintained through harmonization and published in the coremif
Convenience copies of content that is not IP protected by the code system owners
Access to or documentation about the rest of the value sets
May be deferred until after mid-May
Integration with HTA JIRA workflow for change requests for External Terminologies
Need to begin working with HTA to figure this out
Carol and Reuben are both on the HTA and they are requested to keep this discussion going in HTA
CIMI/SOLOR (Keith Campbell)
Confirm in Sydney with Keith if we can make the SOLOR interface look like the loinc.org interface stuff for browsing
Need to continue discussion in San Antonio (or afterwards)
On this week's vocabulary WG call we should decide if we want a joint call with CIMI around these topics
LOINC value set definitions interface for IGs
Need to check this in UTG to make sure it works the same as it does in FHIR terminology pages
For the UTG (sourced from V2, V3, and CDA) they may not work properly; this may be a sign of an IGP issue; details unknown at this time
There may have been a URL change from LOINC that has not yet been implemented in the IGPublisher for the value sets? Needs verification.
Need to discuss with LOINC how best to approach (post first release)
IG terminology access in general
this is a longer term late 2020 or in 2021
Call adjourned at 1:02PM EDT. Next call is scheduled for Tuesday July 7 at noon EDT.
Type your task here. Use "@" to assign a user and "//" to select a due date.