Skip to end of metadata
Go to start of metadata

This page includes all open UTG tasks as of 5/29/20 categorized by milestones. 

Tasks to be addressed post-initial release of UTG Content and pre-Pilot test (Pilot test week of 5/11):

Task Name

Task Category

ResourceStatusComment (if applicable)
Fix coremif generatorContentLloyd
1.0.0 mif is identical to 1.0.18 mif

Enlist Frank to do final test V2 Resources

ContentFrank

Fix Table 0910 IssueContentTed

Unify use of 'status'ContentTed, Grahame
Product families are using different status values. Need to determine how to address this.
Unify use of 'publisher'ContentTed
Publisher field varies across product families
Deprecated field using codes instead of dateTimeContentTed
For v2
Determine how OIDs will be generatedContentTedDONEsee OID Generation
Look into rim-classifier-class-code propertyContentTed
May be a duplicate
Add Scripts to Enable Changes to Resource HistoryWorkflowTedIN PROGRESSManual unix scripts for now, will automate in Jira later

Allow User to Re-Cast Vote

WorkflowJosh

Come Up A Better Way to Represent 'Draft A Proposal'

WorkflowJosh, Ted

Draft a Proposal is done after you enter most proposal information. Perhaps use "Define Change Detail".

Rework Product Family Check BoxesWorkflowTed, JoshDONE

V2 Vocabulary (Including Tables)

Unified Vocabulary (Including Concept Domains)

V3 Vocabulary 

Other (do we need to mention CDA here?)

Remove CIMI

Rename UP ProjectWorkflowTed, JoshDONEShould be something like 'UTG Terminology Change Proposals'

Obtain Approval and Counts for Final Voting Weights (from SGB)

WorkflowTed

Configure Final Voting Weights and Requirements

WorkflowJosh

Configure Notifications for UTG Proposals by Workflow StateWorkflowJoshDONE

These filters, along with a link to opt-in (subscribe), are:

Consensus Review:   https://jira.hl7.org/issues/?filter=13111

Meeting Needed:   https://jira.hl7.org/issues/?filter=13114

Rejected:   https://jira.hl7.org/issues/?filter=13113

Sent for Implementation:   https://jira.hl7.org/issues/?filter=13115

Withdrawn:   https://jira.hl7.org/issues/?filter=13112

Ensure Version History Link Works

IG PublisherGrahameDONEThis is on the bottom banner of the rendered pages

Ensure Objects are Listed Alphabetically

IG PublisherJessNeeds QA

Found in Content Testing. Fixed in one place but not every. Just main Value Sets page need fixing.

Redirects Not WorkingIG PublisherTedDONE
Update UTG Editor to support added extensionsUTG EditorGrahame
Need to see what extensions are missing. Create Zulip record.

Create Structured Guidance for UTG Resources to Support v2, v3, CDA, and fhir

DocumentationJessDONE

Floyd may be able to help for V3 and Rob Hausam for FHIR. Done for Pilot.

Document all Vocabularies that are Out of Scope (structural, ballot-bound)

DocumentationTedIN PROGRESS

Convenience copies out of scope for maintenance AND Ballot-bound content

Contact all Individuals who submitted an applicable Notice of Intent to Ballot (NIB)

Pilot PrepJessDONE

Discuss Craig's V2 HL7nnnn Proposal

Pilot PrepTed, Carol, CraigDONE

Create Jira logins for testers

Pilot PrepJoshDONENeed to verify permissions
Create Jira logins for reviewersPilot PrepJoshDONEOSG voters and Super voters have been configured per Working Group. Anyone with a Jira login can participate

Hold Training session for testers

Pilot PrepTed, JessDONEHeld on 5/26

Run through harmonization process with UTG tooling

Pilot PrepTed, JessIN PROGRESS

Unify ObservationInterpretation

Pilot PrepRob Hausam

Tasks to be addressed post Pilot-testing with the addition of any critical items that come out of the Pilot Test:

Task Name

Task Category

ResourceStatusComment (if applicable)

Define Process for External Proposals

WorkflowJosh, TedDONEMight use check box that acts as a blocker

Checkbox Bypass for Republishing New External Content (Before New HTA Workflow Link is Ready)

WorkflowCarol, Julie
Need to re-discuss with HTA

Tasks to be addressed prior to large-scale rollout (around San Antonio timeframe):

Task Name

Task Category

ResourceStatusComment (if applicable)

Locate and Document Code and Processes to Create Cached Local Images for External Standards

ContentTed

Needs discussion with Ted, Lloyd, Grahame

Update uris from Canada

ContentTed, Dave T
Need to be checked first.  Ted needs to go over this with Andrea M and Beverly K

Create Manifest for Ballot-Bound Content

ContentTed
Ted must create the manifests for the ballot-bound content in all the product lines.  This is to properly handle the erroneous submissions (see task ballot bound content below)

Expansion Versions Date for V2 Value Sets Incorrect (Should be UTG Version)

Content

Grahame

NEEDS QA

Determine if Expansions Should State 'Active Codes From' Instead of 'All'

Content

Grahame


Goes on PZR

Some V2 Concept Statuses are Listed as both 'A' and 'Deprecated'

Content

Ted


Need a list of which ones. These are wrong in the source.
Add Copyright Statement for All External Code Systems with ContentContentTedTBD - 1.1.0SNODENT and HealthcareProviderTaxonomyHIPAA have content. HPC, Iso_3166_2, MediaType, PHManufacturersOfVaccinesMVXCDCNIP, PHRaceAndEthnicityCDC (dup), and PHVaccinesAdministeredCVXCDCNIP display a subset of content (unsure if action needed for those).

Update R2.0 CDA Domains (Add them as Synonyms)

ContentTed
Ted thinks he missed one.

Should Table Content Point to Particular Version of CS?

PolicyTed, Vocab, V2TBD - Post 1.1.0Yes, agreed between Ted and Carol.   Ted to add property for this for v2tables..xml, and to write up the instructions for the value to be placed in there for Dave.   Update:  No, on discussion with Lloyd. Needs review with Carol.   It may need to be done for the ballot-bound V2 code systems.
Template Change for Multiple CLDIG TemplateLloyd

Create tabs for Naming Systems (Identifier Systems, Code System Identifier Registry Items)IG TemplateTed
Per Lloyd
Fix Link for 'Propose a change'IG TemplateTed

Right now this goes right to Jira and people are entering many tickets without understanding the process. Should be linked to the Terminology at HL7 page. 

Steps to propose a change as a subpage of vocabulary maintenace at hl7
streamlined and links for further info, then link to jira project
if this is the first time you are proposing, go to...

Workflow Handling of Ballot-Bound ContentWorkflowJosh, Ted

1.  When in a proposal, reject on submit validation and notify submitter that this content is not maintained through the UTG Process.

2.  When a new spec version normative is released (any product family) the de-facto new terminology object in that new version that are ballet bound get imported in the SoT workflow.  Operations to do this must be defined psst UTG initial release (Ted)

Create Script to Enable Changes to Resource HistoryWorkflowJosh, Ted

Document List of Ballot-Bound ContentContentTed
Could have a tab for Ballot-bound content (CS, VS, etc.) as well. At least document on Ballot-Bound Terminology Content

Implement HTA Interaction

WorkflowTed, Josh, Julie

Change Handling for External Content Change Requests

WorkflowJosh, Ted

Coordination required with each organization that we have an agreement with. Discuss with HTA

Automate Push to GitHub

WorkflowDevelopment Resource

Modification of utg.xml file in branch for version ID

WorkflowJosh, Ted80%

Manual first (must document process steps), automate later. Just need to document the steps.

Modification of utg.xml file for CI Build version updates

WorkflowJosh, Ted80%

Manual first (must document process steps), automate later. Just need to document the steps.

Document Manual Workflow for Publishing a Release

Workflow/PublishingTed, Josh, Grahame

Add custom field that pulls status of branch at proposal draft

WorkflowJosh, Ted

Needs revisiting to see if it is something we really need to fix or not

Add validation check at issue submission to ensure branch has been committed

WorkflowJosh, Ted

Reload Page Upon Vote

WorkflowJosh

Add Ability to Report a Tooling or Content Issue

WorkflowJosh, Ted50%Need to have a way to report tooling issues. Maybe something in the Confluence Page (email or chat log)

Create Workflow for when New CS or VS is Proposed

WorkflowJosh, Ted

Involves new version number, utg.xml updates, control manifest edits, all committed with GitHub. Consensus review needs to add manifest entry so it renders. Needs to be documented.

Consider Renaming 'Change Objects' to 'Related HL7 Artifact(s)'

WorkflowJosh, Ted

Validate Proforma ballot ticket

WorkflowJosh, Ted

Bypass Consensus Review and go Directly to Approved

WorkflowJosh, Ted

Fix R4 Toolkit

UTG EditorGrahame

Fix 'Enumerated' Radio Button when editing Value SetsUTG EditorGrahame

Add Ability to edit Lists (Manifests) in EditorUTG EditorGrahame

Verify Generated CoreMIF through Lynn's Tooling (V3 publishing)

PublishingTed, Lynn

V2 Publishing Database Interfacing (V2 publishing)

PublishingTed

FHIR Pages Update Integration (FHIR publishing)

PublishingTed

Fix Help > About

Vocab ServerGrahame

Server will not start without CDA folder present

Vocab ServerGrahame

Add Time Stamp to Date on CI Build

IG PublisherGrahame

Bug with Value Set's Displaying 'All Codes From' When Not True

IG PublisherGrahame

Update Verbiage on Rendered Pages

IG TemplateTedIN PROGRESS
Describe History Tracking in Background PageIG TemplateTedIN PROGRESS

Document how to check Status of Branch

DocumentationTed, Josh

Sourcetree should notify if master has been updated so you can look, and decide to pull or disregard

Document Use of Control Manifests for Releases

DocumentationTed

Document how UTG will use Naming Systems

DocumentationTedDONE

Discuss Education with Sadhana and Education Committee

EducationTed

There are 4 categories of target audiences: community at large (overall description), HL7 membership and vocab users (access and download), reviewers (getting login w/ permissions, understanding voting, viewing content, etc.), proposal writers (tooling)

Create Training Video for Submitting Proposals

EducationJess

Create Training Video for Reviewing Proposals

EducationJess

Final System TestTestingTesters

Tasks to be addressed in Release 2 (Summer 2020):

Task Name

Task Category

ResourceStatusComment (if applicable)
Discuss How to Address FHIR Value Sets in Trial StateContentTed, Grahame, Lloyd

Add Provenance Resources (History)ContentGrahameDONE
Import V3 History from CoreMIFContent
DONE
Import V3 History from DatabaseContent


Import Inferred V2 HistoryContent


Add HL7VersionIntroduced

ContentGrahameDONE

Add Extension for Historical Ids

ContentGrahamWON'T DOWill be done in Naming System

Document Date URIs were Taken From / Effective Since

ContentTed, Dave T
Requires new element in Naming System

Determine How to Access SOLOR Content with SOLOR API

ContentTed, Keith

Automate Update of Manifests for Newly Added CS and VS

ContentGrahame

Add Support for Printname and Description in Multiple Languages (CodeSystem.concept.designation.*)

ContentGrahame, LloydDONEDone as far as the tooling and rendering. There may be more translations added later.

Import of Foreign Language Translation Files (Base or Supplement?)

ContentDave TDONEDone as far as the tooling and rendering. There may be more translations added later.

Improve Narratives and Descriptions in the Manifests (List Resources)

ContentTed

Render the Lists (A List Resource Display Tool)

ContentTed

Publisher Values need Unification

Content

HL7 Community



Copyright statements differ for each product family

Content

HL7 Product Line Management Groups



Include Capitalization of Steward Name

ContentTed

Content Unification to Address Standard Naming Conventions Across Product Families

Content

HL7 Community



Address Objects With Non-Unique Symbolic Name Across V2 Content

Content

HL7 Community



Many V2 Code System Descriptions Refere to XAD Segments (Should be Data Type)

Content

HL7 Community



FHIR I to Review List of Schema Bound Code Systems and Determine if any need to be moved to UTG

ContentFHIR I

Enable Updates back to Lantana

ContentTed, Rick, Sean

Compile List of VSAC Issues

ContentTed, Rob M

Handle Updates of External Content

ContentJosh, Ted

Coordination required with each organization that we have an agreement with

Fix Missing Line Breaks in V2 Code Definitions

ContentTed, Dave Trig
Ted to discuss with Lloyd and V2 best way to handle line breaks in IG. HTML markup doesn't support embedded carriage returns.  update:  speak with Grahame about possible issues with the processing of markdown for the definition test blocks.

Additional Characters Being Added to Concept Domain Definition

ContentDave Trig
Concept domain definitions are stored in markdown language, and underscore is a special character in markdown, indicating italics.  This is why the underscores are escaped with a backslash character.  Without the backslash, your example, “Employee_Employer_statusCode” would render in markdown as “EmployeeEmployerstatusCode”, which we do not want.  If you still want definitions in markdown language, then the backslashes are necessary. Ted to talk to Lloyd to see if anything can be done.   Bulletin: Ted to follow up by asking Eric Haas.   

Table 0340 Should Not Be Listed as Concept Domain Only

ContentTed
This is a much larger issue than at first appeared.   The codes historically published are only guidance notes, and never intended to be used in messaging instances in v2.  They have bee deprecated some time ago, and there is no current active HL7 content for this table. It does need to be a concept domain only, but work has to b e done to fix it properly. UTG description tuned up to better describe the situation

Improve Automation of steps for Submitters to establish BitBucket/SourceTree

WorkflowDevelopment Resource

Link to Documentation based on state of Proposal

WorkflowJosh, Ted

Add validation check at issue creation that searches for possible duplicates

WorkflowJosh, Ted

Automation of Ballot-Bound Content Handling

WorkflowJosh, Ted

Consider Removing 'Create Issue' from Bottom of JIRA Open Issues Page

WorkflowJosh, Ted

Refine Sponsors to Include Dropdown of WGs or Allow Text Entry

WorkflowJosh, Ted

Consider Allowing Search for Existing HL7 Artifact

WorkflowJosh, Ted

Remove Comment Field Upon Clicking 'Draft A Proposal'

WorkflowJosh, Ted

Automate Transition to Merge Branch from BitBucket into GitHub Trunk

WorkflowJosh, Ted

Status Code is Missing in Expansion

IG PublisherGrahame

Make Property URLs Clickable

IG PublisherGrahame

Allow Way to Differentiate Objects with same <name>

IG PublisherGrahame

Allow a Way to Search for Objects

IG PublisherGrahame

Allow Import of Multiple Stewards

IG PublisherGrahame

Create Diagram to show how Templates, Construction, and Recording of Process is in UTG

DocumentationTed

Add Release Documentation for Individual Changes in a Release

DocumentationLloyd

Tasks to be addressed post-Release 2:

Task Name

Task Category

ResourceStatusComment (if applicable)

Support Supplements and Fragments

ContentGrahame

Add Support for ConceptMap

Content/IG PublisherGrahame

Art Décor Publishing

PublishingTed, Alexander

FHIR I to Review Internal FHIR Value Sets and Determine if any need to be moved to UTG (and create manifest)

ContentFHIR I

Agreements for Republishing New External Content

ContentCarol, Julie

Figure out Process for Creation of New IG

WorkflowVocab, FHIR I

Response will use HTA template but go through Jira and back into UTG

Add JIRA Configuration for Watching IGs in Progress

WorkflowTed, Josh

Properly Render Extensions

IG PublisherGrahame

Address Difficulty Navigating Pages with Many Columns

IG TemplateHL7 Community
Determine if some columns could be removed for ease of use

Improved Display of Multiple Hierarchy

UTG Editor

Grahame




CLOSED MILESTONES AND RELATED TASKS:

Tasks to be addressed prior to the initial release of content (for release date of on or around May 1; most fixes need to be done manually):

Task Name

Task Category

ResourceStatusComment (if applicable)

Update CDA Value Sets

ContentTedDONE

Set Dates for Context Bindings with MnM

PolicyTed, Grahame, Lloyd, Dave TrigDONETed and Lloyd concur that this has always been reset to the coremif release date, and there is little reason to put much extra effort into discovery of the real dates way in the past and try to apply them.   Set all dates for these to January 1, 2020 as boilerplate in the next import.
Address Missing Code 'att' for AttachmentsContentTedDONENeeds to be added manually post-last load. May still be an issue since we are referencing R4. Also need to discuss with Grahame.

No Expansions for Several Value Sets (Reference is Incorrect)

ContentTedDONELookup when VS does not have a local CS.  Hard to find until we remove the thousands of other errors so we can find these
Publisher Not Displaying OID in Resource of External Code SystemsContentTedDONE

Implement Release Versioning

ContentTed, GrahameDONECoordinate folders with DJ. Plan is set.  Only remaining item is figure out the workflow to document changes going forward.  Requires publisher v0.88 or later.

Create UTG logo and color scheme

IG TemplateTedPUNTThe one that Grahame and Ted threw together is what we are going with since we cannot get any input or response from anyone else at HL7.

Provide Text for Disclaimer banner

IG TemplateTedDONEI think; all banners actually look ok right now (Ted)

Extend Capability of the FHIR Release Process to do UTG Release

IG PublisherGrahameDONE
Fix Issue with Value Set Expansion using Is-A as FilterIG PublisherGrahameDONESomething is broken with the value set expansions on the UTG publisher build - many of them are not expanding a hierarchy with include.filter.op value="is-a". Details on one that illustrates the problem can be found in the Google Doc at https://docs.google.com/document/d/1hM3TubYKop1XWei7ls5j8O9LxfGUd-LU7gacGnXlX8k/edit?usp=sharing
Allow Expansion of Value Set FragmentsIG PublisherGrahameDONE
Add Warning when Expansion is Based on Value Set FragmentIG PublisherGrahameDONE

Integration of Core MIF Generation to UTG Build

PublishingGrahame, LLoyd, TedDONEready to go once a new coremif is generated, which cannot happen until the extensions cleanup - generator breaks now until this is done

Generate Updates on UTG Current Releases Page in Published Script

PublishingTedDONE

Generate the Initial Release

PublishingGrahame, TedDONEPlanned for May 3-4

Create the Workflow for when Content Issue is Identified but No Proposal for Change

WorkflowJosh, TedDONETed will review with Josh.

Tasks to be addressed prior to the last import of content. These must be completed IMMEDIATELY, prior to April 24 (pushed out three weeks as content issues are still being addressed):

Task Name

Task Category

ResourceStatusComment (if applicable)
Add Usage Notes for V2 and V3 ContentContentDave TrigDONE
Fix URIs for a Handful of ExtensionsContentLloyd, TedDONEMost of the bad URI errors are in extensions to be removed; revisit once import addressing the documented extensions errors is done
Remove Extensions No Longer Being UsedContentDave TrigDONERemove code-system-legalese and resource-history extensions
Remove V2 'generate' PropertiesContentDave TrigDONE

Fix CLD Value Being Assigned 1 By Default

ContentDave TrigDONE

Missing V2 Usage Notes, Comments, Comment as Pub

ContentDave TrigDONE
Define All ExtensionsContent LloydDONEExtension Google Doc is Up-to-date (minus the new ones - need to update)
Fix Display value being populated instead of Code value where extra language designations existContentDave TrigDONEExample is v3-RoleCode
Fix incorrect system URI for hl7TermMaintInfraContentDave TrigDONENeeds to be http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra
Determine why Binding Strengths are not RenderedIG PublisherDave TrigDONENot publisher issue, importer issue
Errors thrown from Concept Domains about Extensions not being allowedContentTed, LloydDONE
Valueset-hl7-assocConceptProp extension 'not allowed'ContentTed, LloydDONE
Import Values for Supported PropertiesContentDave TrigDONENeed to import extension properties

Import Committee for FHIR Objects

ContentTed, LloydDONEthis is a Grahame issue; Ted needs to raise it with him. Was supposed to be fixed inn publisher v0.83, but still seems to be some problems.
Add extension for Naming System version and populate ContentLloydDONEVersions were added post R4 but IGs reference R4. Extension was added but needs to be populated. Extension is http://terminology.hl7.org/StructureDefinition/ext-namingsystem-version
Many FHIR Links are not resolvingContentTed, GGDONESee consentAction. Need to verify with Grahame that they will go away when we do first release.
Internal build error for several resourcesContentTed, GGDONEEx: vs-v2-0725 which likely references v3. Might be after last import, need to investigate.
Fix FHIR Import issuesContentTed, Lloyd, GrahameDONEMight be issue when canonical URI and ID don't match. Policy says that they should match. Need to discuss with Grahame.
New Tasks for next import from 3/28-4/9:


Added by Ted as a result of weekend work with Lloyd
In conceptdomais.xml, duplicate binding strength property entries (see AcknowledgementDetailCode)ContentDave TrigDONEWas due to an invalid extension and a populated concept property as well. 
Remove resource-concept-binding-strength extensionContentDave TrigDONE

There is an extension being generated in conceptdomains.xml which should have been removed; it was a replaced with properties like these:

<property>
<extension url="http://hl7.org/fhir/StructureDefinition/resource-concept-binding-strength">
<valueCode value="CWE"/>
</extension>
<code value="contextBindingC1-valueSet"/>
<valueString value="2.16.840.1.113883.1.11.19638"/>
</property>

have not been removed.  They need to be as they were replaced with properties.

For V2 tables with code system information mapped to FHIR CodeSystem resources, it is unclear where the Effective Date value is mapped to. For example, in 0001 (Administrative Sex) the Effective Date value is "01.11.2000" (1-Nov-2000). However, this date does not appear in the generated FHIR CodeSystem (http://terminology.hl7.org/CodeSystem/v2-0001). Instead, CodeSystem.date has a value of "2019-12-01T00:00:00+00:00".ContentDave TrigNON ISSUEIt is the effective date of the table, not the Code System. Ted will discuss with Reuben why this isn't an issue. 
For V2 tables with code system information mapped to FHIR CodeSystem resources, is HL7 Version Introduced (from Code System Version Information in Chapter 2C) deliberately not being mapped to the FHIR CodeSystem?Content/PolicyDavid Trig, TedNON ISSUESee above. 

Populate extension for http://terminology.hl7.org/StructureDefinition/ext-mif-assocConceptProp

ContentTedDONE

Turns out an additional extension is needed for value sets that we didn't think we needed (incorrect material there from original IMO work). URI for the associated concept properties is now http://terminology.hl7.org/StructureDefinition/ext-mif-assocConceptProp not the one in there from IMO at the FHIR location. Lloyd created the new extension over the weekend.

Ted needs to talk to Lloyd.

Need <title> in NamingSystem generated resourcesContentDave TrigDONE

this will get rid of many errors.  It must be populated with the Code System name from the coremif or the v2 database.  It is a new extension http://terminology.hl7.org/StructureDefinition/ext-namingsystem-title


Incorrect version-introduced values in V2 Tables ContentDave Trig, Ted, BrianDONE

In the V2Tables CodeSystem, the value for version-introduced (in CodeSystem.concept.property.value, where property.code="v2-version-introduced") all have a value of "2.9"

Discuss with Brian Pech, might need property for tables-version for v2-tables.xml and should be set for 2.9 initially. 

Ted to add additional property for table introduced HL7 version.  Dave to populate with the mob column for version introduced.

Property for version the table was a introduced (column HL7tables.version_introduced in mdb) is:   

"v2-version-tbl-introduced"

Note that a his integer must be used to look up the version id in table HL7Versions.  The column with the integer is version_id, the column to be put in the string property is hl7_version.

Property that we previously used for introduced now refers explicitly to v2 cs and vs.n. The value for this property should be set to "2.9";  the name of this property is now:  

"v2-version-csvs-introduced"

This will be updated manually after the last import for those tables that a are associated with V3, FHIR, or External code systems and/or value sets.



Value of V2 CodeSystem.valueSet does not include a version (as is allowed for the canonical(ValueSet) data type PolicyTedWILL NOT DO 

Need clarification from Reuben. Probably requires a content change. 

I updated the description to make the requirement more clear.

For V2 tables with code system information mapped to FHIR CodeSystem resources, the CodeSystem.valueSet element is included for the implicit value set consisting of all the concepts in the CodeSystem. However, the value of CodeSystem.valueSet does not include a version (as is allowed for the canonical(ValueSet) data type e.g. "<valueSet value="http://terminology.hl7.org/ValueSet/v2-0001|2.1.0"/>" as opposed to "<valueSet value="http://terminology.hl7.org/ValueSet/v2-0001"/> . I would suggest this be included.

Do only for those based on to FHIR code systems.  Do manually after last import

Discussed with Lloyd and he believes this should NOT be done, especially in light of the Vocab WG polices that the v2.x published spec is a snapshot of the current tables but for all nonn-ballot–bond tables the latest versions should be used.

Error in concept domains.xmlContentDave TrigDONE

The canonical url and id must match.  we currently generate:

<id value="conceptdomains"/>
<url value="http://terminology.hl7.org/CodeSystem/ConceptDomain"/>

Needs to both be the same as current id:  "conceptdomains"

Remove HCPCS and the four NUBC Code Systems from externalContentTed to remove manuallyDONE

Per HTA decision on 4/1/20


Add the entry for table 396 to the v2 code system manifestContentTedDONE
The deprecation information extension is still be generated. Needs to be removed.ContentDave TrigDONEThe entry http://hl7.org/fhir/StructureDefinition/resource-deprecationInfo is still being generated in a bunch of the code systems and value sets.  We agreed in the extensions document that this would be done later in Provenance.  This needs to be removed from the import.

There are still Open Issue extensions in some of the resources, they have not all yet been removed.  e.g. 

v3/codeSystems/v3-AcknowledgementType.xml.   The extension http://hl7.org/fhir/StructureDefinition/resource-openIssue is unknown, and not allowed here

ContentDave TrigDONE
Fix URI for  <version> element in the NamingSystem resource generation - the extension has been createdContentDave TrigDONEthe URI of the extension is 

<url value="http://terminology.hl7.org/StructureDefinition/ext-namingsystem-version"/>

In many of the v3 resources, the id of the object has a hyphen in I and <name> does not - e.g. 

<name value="xLabProcessClassCodes"/>

<id value="v3-xLabProcessClassCodes"/>

The <name> and <id> must match, and neither can have hyphens; these can only be in <title>

ContentDave TrigDONE

This was originally fixed for <name> but not for <id>. Needs fixing.

<name> can have underscores, but no other punctuation. <id> can have periods and dashes. URL must end with the id
<name> and <id> do not need to match
<name> needs to be UpperCamelCase
<title> is unrestricted and should hold what we extract from V2 mdb and V3 coremif for the names.
<id> is typically lower-case, though that's not mandatory

Dave did fix the <name> of some Value Sets so that they are upper camel case

The generated NamingSystem resources need to have added to them the url elementcontentDave TrigDONE

add 

<url value="http://terminology.hl7.org/NamingSystem/nnnn"/>

where "nnnn" is the same value as used in the <id> (previously was specified to use <name> but that's incorrect)

Import Deprecated status and datesContentReubenDONE
  • No labels