HarmonizationSummary-20100713

Harmonization Review Summary (date in title)

Prepared after Technical Review for August 2010 Meeting

Change only the right-most three columns. The left is auto-generated from the Harmonization spreadsheet

Item #	Work Group	Proposal Name	Proposal ID	Notes	Result	Vote
010101	MNM	Add Missing ValueSets for Codes added to Structural Code Systems	RIMR3B1-01	ok. VML generated	result	^-v-?
010102	MNM	Correct Naming Properties on Selected RoleClass codes	RIMR3B1-02	ok. VML generated	result	^-v-?
010103	MNM	Correct definitions around contextConductionStyle and new RIM	RIMR3B1-03	ok. VML generated	result	^-v-?
010104	MNM	Correct errors and omissions in the ActRelationship event timing codes	RIMR3B1-04	ok. VML generated	result	^-v-?
010105	MNM	Fix criterion stuff	RIMR3B1-05 201007-C00-06	ok. VML generated	result	^-v-?
010106	MNM	REMOVE attribute Act.contextConductionStyleCode from RIM	RIMR3B1-06	ok.	result	^-v-?
010107	MNM	Correct definition of class Exposure in RIM	RIMR3B1-07	ok. VML generated	result	^-v-?
010108	MNM	Revise RIM ""quantity-related"" attribute definitions	RIMR3B1-08	Still being evolved on Wiki, in preparation for final submission in ten days.	result	^-v-?
010111	MNM	Fix AddressPartType relationship types	201007-C00-01	After discussion with Mckenzie, will change so that the "hasSubtype" relations will be replaced with a "reversed" relationship named "ComponentOf". This "works" in RoseTree and so forth.	result	^-v-?
010113	MNM	Fix realm codes	201007-C00-04	Ted will suggest somee clarifiactions. It is understood that this is intended as an improvement nbot a change, per se.	result	^-v-?
010114	MNM	Make some MIF enumerations code systems	201007-C00-04	Issue - We have not allowed spaces in concept codes to this point. It tends to break extant tooling. Is there a way to resolve this? This exists in two of the code systems - approval status, and vote resolution, What is best solution?	result	^-v-?
010115	PAFM	Add descriptions to class codes	PA-201008-04	OK	result	^-v-?
010117	STRUCTURE	Relax constraint on CAUS act relationship type code	CAUS-1	OK, but note that this is technically out of scope for RIM, because of active ballot, and fact that this did not arise from a ballot comment.	result	^-v-?
010118	PAFM	Revise codes under ActClass	PA-201008-02	Two problems 1) Out of Scope for RIM in this cycle. 2) Could be as simple as changing formal name to CareProvision with no new code.	result	^-v-?
010202	MNM	Move ISSUE code type	201007-C00-03	Technically fine.	result	^-v-?
010207	PAFM	New concept domains	PA-201008-01	Proposal looks good.	result	^-v-?
010209	PAFM	Add Concept Domain definition for EmployeeRoleType	PA-201008-03	Proposal looks good.	result	^-v-?
010211	PAFM	Add codes to ServiceDeliveryLocationRoleType	PA-CA201008-01	Proposal looks good. Did the submitter check the value sets to be sure any effects on the value set expansions are those that are desired? Verify OK to adds codes under VS ServiceDeliveryLocationRoleType	result	^-v-?
010212	PAFM	Add concept for PersonalRelationshipRoleType	PA-CA-201008-02	Proposal looks good.	result	^-v-?
010213	PATIENTCARE	New concept domains	PC-CA201008-01	Not sure what the third item is? Move the existing concept domain to be under the new one? Also only 2 items were noted in the summary table, but 3 are written up. Clarified with author.	result	^-v-?
010214	MEDREC	Create Concept Domain ActMonitoringProtocolType	PHARM-CA201008-01	Good Proposal	result	^-v-?
010220	PHER	Add new codes and concept domain ActAntigenInvalidReason	PHER-CA201008-01	OK proposal	result	^-v-?
010221	PHER	Add new concept domain ImmunizationObservationType	PHER-CA201008-02	Good Proposal	result	^-v-?
010222	PHER	Add new concept domain PatientImmunizationObservationValue	PHER-CA201008-03	Good Proposal	result	^-v-?
010223	PHER	ActNoImmunizationReason technical correction and new codes	PHER-CA201008-04	Good Proposal	result	^-v-?