CSCR-096-OO-Assign appropriate domains to Act.code, Role.code, and Entity.code

Back to Clinical Statement Change Requests page.

Submitted by: Patrick Loyd	Revision date: 15-Jan-2009
Submitted date: 15-Jan-2009	Change request ID: CSCR-096

Issue

• ActCode, RoleCode, and EntityCode have been dropped as concept domains and remain only as codeSystems. Therefore, no message models (DMIM, RMIM, etc.) should bind an attribute to any of these three codeSystems.

Recommendation

• Remove all usage of ActCode, RoleCode, and EntityCode

Rationale

• At the November 2008 Harmonization Meeting (Las Vegas), it was approved to remove the concept domains ActCode, RoleCode, and EntityCode. They will remain as code systems. Therefore, no class should assign any attribute to use any of these three prior domains.

Discussion

• What is the right policy for binding vocabulary in 'pattern' models?

Recommended Action Items

• The following class.attributes need to change their binding from the generic to specific concept domains and value sets.
  • SubstanceAdministration.code - ActCode = change to ActSubstanceAdministrationCode (existing)
  • Supply.code - ActCode = change to SupplyType (new)
  • Procedure.code - ActCode = Change to ActProcedureCode (existing)
  • Act.code - ActCode
  • Organizer.code - ActCode
  • Animal.code - EntityCode = change to NonPersonLivingSubjectEntityType (existing)
  • Entity.code - EntityCode
  • Role.code - RoleCode = change to RelatedEntityRoleCode (new)
  • Informant.functionCode - ParticipationFunction
  • Performer.functionCode -ParticipationFunction
  • ObservationRange.code - ObservationType
  • Criterion.code - ObservationType = change to ObservationEventCriteriaType (new)
  • ControlActEvent.code - ActCode = change to HL7TriggerEventCode (existing)

Resolution

29-Jan-09 - Will postpone the discussion until we have had a chance for enough people. Should not go back into ballots until domains are "removed".