This wiki has undergone a migration to Confluence found Here
HarmonizationSummary-20120313
Jump to navigation
Jump to search
Harmonization Review Summary (date in title)
Change only the right-most three columns. The left is auto-generated from the Harmonization spreadsheet
Item # | Work Group | Proposal Name | Partial Description | Proposal ID | Notes | Result | Vote |
010000 | MNM | Change ParameterItem.semanticsText to be a mandatory SC | Change ParameterItem.semanticsText to be a mandatory attribute and change its datatype to be SC. | JD-001 | Simple, but needs two other pieces. First should it not be SC.NT (in keeping with other RIM SC attributes) and it needs a Concept Domain defined and assigned to it as the RIM terminology constrint. (Which makes this both a RIM and a VOC proposal. | result | ^-v-? |
010001 | MNM | Actions on Deprecated Material | A detailed review of every RIM item and RIM or Data Types -vocabulary item that has been formally (or in a few cases, almost formally) DEPRECATED has been undertaken. We have agreed to take action on | MnM-DeprecatedActions | Complete - Annual Standing Item: Proposal to delete all RIM and Vocabulary items that were deprecated in 20087 and earlier, per policy adopted at November 2011 Harmonization. Involves removing 8 RIM Attributes and retiring 1 Concept Domain, 8 Code Systems (in their entirety), 2 coded concepts, and 2 value sets. | result | ^-v-? |
010002 | MNM | Role Class Codes Require Removal | Updated: There are 6 Role Class codes appear to be out of place in the Role Class hierarchy. The codes are: CHILD, CRED, NURPRAC, NURS, PA, PHYS. Currently these are all siblings of ROL. Research into | AJK-01 | Revision of Austin Kreisler's proposal. This is based on a careful review of how this arose. Recommendation is to RETIRE all six codes immediately. They appeared in mid-2008 by chance (see document) and have NEVER been a member of a Value Set. | result | ^-v-? |
010003 | MNM | Role Class Ontological Clean-up | To undertake a clean-up of the concepts and their relationships in Role Class Ontological | MnM-Ont | From Nov 2011. Table (in yellow) should show "Changes to 6 Codes" rather than changes to one code system. | result | ^-v-? |
010004 | MNM | Revise ParticipationMode definition | Revise ParticipationMode concept domain definition. | MnM-CA201203-02 | Complete. Revises definition of a Concept Domain | result | ^-v-? |
010005 | MNM | Definition for NullFlavor | Provide a definition for NullFlavor concept domain and description for NullFlavor code system | MnM-CA201203-01 | Complete. Provides missing definitions for NullFlavor Coencept Domain and Code System. | result | ^-v-? |
010006 | NoCommittee | Event Location – Role Class Code | Request to add a value to HL7’s Role Class coding system. We need the ability to capture the role of a place where something, an event, happened. The proposed code will be known as EVLOC – event locat | 2012.Vocab.DMW01 | Almost complete - Structural Vocabulary - Please update and add the formal namie parameter for the RoleClass when it is used with this code.
Please indicate sponsoring Work Group. |
result | ^-v-? |
010007 | ORDERS | RoleClass Contaminant (CNTM) is an Ingredient (INGR) | Add a concept and code to RoleClass named Contaminant with code CNTM and specializing Ingredient (INGR) | [1] | PLEASE RESUBMIT this Document. In its current form, it CAN NOT be edited in Microsoft word. Clicking anywhere below the header box, jumps to the bottom of the document | result | ^-v-? |
010008 | PAFM | Add new ActRelationshipType | Need to a relationship type to indicate the association between two encounters. | PA-201203-01 | INCOMPLETE. Missing value for property:isDocumentCharacteristic; missing formal names (see entriy prompts in the middle of your "Reccommendation"). Needs a Proposed ValueSet for which the definition is this new code and all of its specializations. Nominal value set name would be ActRelationshipLink. | result | ^-v-? |
010009 | PATIENTCARE | CONC Concern class code move | Move the CONC Concern class code from its current location under OBS to be an immediate child of ACT. This is considered a technical correction, since it is believed that placement under OBS was count | 2012.PC.RS01 | Structural Vocabulary - primarily a move of a code within the ActClass hierarchy. Please re-post using the current Word Template that includes a section in which to tabulate the kinds of Vocabulary changes being requested. | result | ^-v-? |
010010 | MNM | pauseQuantity and moodCode clarification | Alter and clarify the documentation of RIM class attribute ActRelationship.pauseQuantity, in relation to how it operates between source and target acts that have differing moods. This behavior is not | 2012.MnM.RS01 | Complete - Change to documentation of ActRelationship.pauseQuantity only | result | ^-v-? |
010011 | ORDERS | LivingSubject developmentalStage | Add an attribute developmentalStageCode to class LivingSubject: | [2] | notes | result | ^-v-? |
002000 | MNM | Definition for ControlActReason | Update ControlActReason concept domain definition | MnM-CA201203-03 | Complete. Revises definition of a Concept Domain | result | ^-v-? |
002001 | VOCAB | Add property to Value Set and Code System | Add one property to both terminology model components: value set and code system to indicate the specified is in a “freezing state” that prevents further concepts be added to it. | HL7 VOC-201203-01 | ??? Doesn't the "isImmutable" property on Value Sets already do this? Why not just extend that to apply to Code Systems??? | result | ^-v-? |
030000 | INM | Definition for Sequencing concept domain | Update definition for Sequencing concept domain. | InM-CA201203-01 | Complete. Update to the definition of a single Concept Domain | result | ^-v-? |
030001 | MEDREC | Medication Generalization Role Type | Update the concept domain description and examples of Medication Generalization Role Type, in line with the Ontological Role Class clean-up | [3] | notes | result | ^-v-? |
030002 | ORDERS | New lab concept domain | Add concept domains to allow describing lab orders referred or redirected, as well as capturing reportable test destination. | OO-CA201203-01 | Multiple componenets. Some questions. First, item (4) asks for a binding between a Concept Domain and a Value set, and I suspect these were to be the ones defined in steps 1 & 3, but the names in step 4 do nbot match EITHER of these!. Second, for step 5, how does a "LabResult" differ from any other Observation? What is it that distinguishes this from ObservationValue? And why is this specificity necessary? | result | ^-v-? |
040000 | PHARM | Storage and Shelf Life Type Concept Domains | To add a new concept domain of "Shelf Life Type" as a child of MedicationObservationType, and to add a new concept domain of "Storage" Type as a child of act code | CPM-26 | Mostly correct addition of two concept domains. The spaces should be removed from the proposed ConceptDomains (leaving as UpperCamelCase). | result | ^-v-? |
040001 | PHARM | Combined Dose Form Concept Domain | To add a new concept domain "Combined Dose Form" as a child of "Dose Form" | CPM-21 | Mostly correct addition of single concept domain. The spaces should be removed from the proposed ConceptDomains (leaving as UpperCamelCase). | result | ^-v-? |
040002 | PHARM | Material Form Concept Domain Revision | To revise the description of the parent concept domain for Material Form to reflect the RIM attribute and thereby to remove the existing Vocabulary issue. | CPM-22 | Complete p[roposal for MaterialForm. During review, I would recommend we ask for an update that addresses two items: (1) Should the Existing OpenIssue be removed as a result of this change? And (2) Please propose the retirment of the MaterialForm code system. | result | ^-v-? |
040003 | PHARM | Container Form Concept Domain | To add a new concept domain "Container Form" as a child of "Material Form" | CPM-23 | Mostly correct addition of single concept domain. The spaces should be removed from the proposed ConceptDomains (leaving as UpperCamelCase). | result | ^-v-? |
040004 | PHARM | Act Product Reconstitution Type Concept Domain | To add a new concept domain of "ActProductReconstitutionType" as a child of ActProcedureCode | CPM-24 | Complte. Adds single Concept Domain. | result | ^-v-? |
040005 | PHARM | Disease Qualifier Observation Type Concept Domain | To add a new concept domain of "DiseaseQualifierObservationType" as a child of ObservationType, linked to the observation act class conceptual space. | CPM-25 | Mostly correct addition of single concept domain. The spaces should be removed from the proposed ConceptDomains (leaving as UpperCamelCase). | result | ^-v-? |
040006 | PHARM | Physical Characteristics Medication Observation Type | Add a new concept domain Physical Characteristics Observation Type as a child of Medication Observation Type | CPM-27 | Mostly correct addition of single concept domain. The spaces should be removed from the proposed ConceptDomains (leaving as UpperCamelCase). | result | ^-v-? |
040007 | PHARM | Device Observation Type | Add a new concept domain Device Observation Type as a child of Observation Type | CPM-28 | Mostly correct addition of single concept domain. The spaces should be removed from the proposed ConceptDomains (leaving as UpperCamelCase). | result | ^-v-? |
050000 | RCRIM | RPS Context Of Use | Create a concept domain to enable regulators to bind to external code systems to represent the sequence of headings forming a pro forma table of contents (subdivision headings) applicable to various s | RPS-2012-01 | Incomplete Concept Domain add. Name does not conform to existing pattern of other Concept Domains in this space, which would be nlike. "Act<<ThisName>>Type. Also Is missing three Examples | result | ^-v-? |
050001 | RCRIM | RPS Document Type | Create a concept domain to enable regulators to bind to external code systems to represent the types of documents applicable in their realm. | RPS-2012-02 | Incomplete Concept Domain add. Is missing three Examples | result | ^-v-? |
050002 | RCRIM | RPS Keywords | Create a concept domain to enable regulators to bind to external code systems to be used to identify the code systems to be used to indicate additional metadata applicable to submission content in the | RPS-2012-05 | Incomplete Concept Domain add. Name does not conform to existing pattern of other Concept Domains in this space, which would be nlike. "Act<<ThisName>>Type. Also Is missing three Examples | result | ^-v-? |
050003 | RCRIM | RPS Regulatory Category | Create a concept domain to enable regulators to bind to external code systems to represent the administrative categories applicable to submitted material in their realm. | RPS-2012-03 | Incomplete Concept Domain add. Name does not conform to existing pattern of other Concept Domains in this space, which would be nlike. "Act<<ThisName>>Type. Also Is missing three Examples | result | ^-v-? |
050004 | RCRIM | RPS Regulatory Status | Create a concept domain to enable regulators to bind to external code systems to represent the regulatory status of submissions applicable in their realm. | RPS-2012-04 | Incomplete Concept Domain add. Name does not conform to existing pattern of other Concept Domains in this space, which would be nlike. "Act<<ThisName>>Type. Also Is missing three Examples | result | ^-v-? |
060000 | SECURE | ActPrivacyPolicyType Technical Corrections | Technical correction to the ActPrivacyPolicyType vocabulary approved in November 2011 Harmonization to implement value set bindings. | Security Vocabulary Proposal 2 | Uninterpretable. WHERE doe the tablular displays come from. They are NOT from the standard way of publishing in HL7 ballots today. They look like ancient vestiges from before May 2008. They are very difficult to interpret. because they conflate Concept Domains, Code Systems and Value sets.
What does it mean that the committee want to review before we process. In that case, they will VERY likely miss the next ballot. Why is this called a Technical Correction? Were they added incorrectly in the first place? |
result | ^-v-? |
060001 | SECURE | ActSecurityPolicyType, ActObligationSecurityPolicyType, ActRefrainSecuityPolicyType | <<REQUIRED - Very short general description of the overall proposal. This should be sufficient for someone scanning a list of proposals to determine whether they are interested in this one. Example: “ | Security Vocabulary Proposal 2 | Uninterpretable. WHERE doe the tablular displays come from. They are NOT from the standard way of publishing in HL7 ballots today. They look like ancient vestiges from before May 2008. They are very difficult to interpret. because they conflate Concept Domains, Code Systems and Value sets.
What does it mean that the committee want to review before we process. In that case, they will VERY likely miss the next ballot. |
result | ^-v-? |