This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Open Composite Order Vocab Items"

From HL7Wiki
Jump to navigation Jump to search
Line 5: Line 5:
 
= Vocabulary Items for Composite Order =
 
= Vocabulary Items for Composite Order =
 
*PlacerGroup.code = ActCode (not a concept domain, need to create a new concept domain)
 
*PlacerGroup.code = ActCode (not a concept domain, need to create a new concept domain)
*Observation.code (PEL) = ObservationType (to general a binding, create a new concept domain OrderableObservationType)
+
*Procedure.code (PEL) = ObservationType (incorrect binding domain, create new OrderableProcedureType domain under ActProcedureCode)
*Observation.methodCode = ObservationMethod (maybe OK?)
 
*Procedure.code (PEL) = ObservationType (incorrect binding domain, create new ProcedureType and OrderableProcedureType domain)
 
 
*Procedure.methodCode = ObservationMethod (incorrect binding domain, create a new ProcedureMethod domain)
 
*Procedure.methodCode = ObservationMethod (incorrect binding domain, create a new ProcedureMethod domain)
*Supply.code (PEL) = ObservationType (incorrect binding domain, create new SupplyType and OrderableSupplyType domain)
+
*Supply.code (PEL) = ObservationType (incorrect binding domain, create new ActSupplyType and OrderableSupplyType domain)
*Substance Administration.code (PEL) = ActCode (not a concept domain, need to create a new concept domain, being discussed in Rx WG, we need a subset OrderableSubstanceAdminstrationType)
+
*Substance Administration.code (PEL) = ActCode (not a concept domain, need to create a new concept domain, being discussed in Rx WG, we need a subset OrderableSubstanceAdminstrationCode under ActSubstanceAdministrationCode)
 
*Author.signatureCode = ParticipationSignature (do we really understand the usage here?)
 
*Author.signatureCode = ParticipationSignature (do we really understand the usage here?)
 
*Consultant.functionCode = ParticipationFunction (concept domain too broad, need sub domain)
 
*Consultant.functionCode = ParticipationFunction (concept domain too broad, need sub domain)

Revision as of 01:32, 16 February 2009

Back to Orders & Observations WG main page

Back to Composite Order page

Vocabulary Items for Composite Order

  • PlacerGroup.code = ActCode (not a concept domain, need to create a new concept domain)
  • Procedure.code (PEL) = ObservationType (incorrect binding domain, create new OrderableProcedureType domain under ActProcedureCode)
  • Procedure.methodCode = ObservationMethod (incorrect binding domain, create a new ProcedureMethod domain)
  • Supply.code (PEL) = ObservationType (incorrect binding domain, create new ActSupplyType and OrderableSupplyType domain)
  • Substance Administration.code (PEL) = ActCode (not a concept domain, need to create a new concept domain, being discussed in Rx WG, we need a subset OrderableSubstanceAdminstrationCode under ActSubstanceAdministrationCode)
  • Author.signatureCode = ParticipationSignature (do we really understand the usage here?)
  • Consultant.functionCode = ParticipationFunction (concept domain too broad, need sub domain)
  • Performer.functionCode = ParticipationFunction (concept domain too broad, need sub domain)
  • ProcessStep.classCode (PEL) = ActClassProcessStep (create new value set)
  • ProcessStep.code (PEL) = ActCodeProcessStep (create new concept domain)
  • ParentRequestReference.classCode = ActClassCompositeOrder (create new value set)
  • PriorActRequest.classCode = ActClassCompositeOrder (create new value set)
  • ProcedureEventCriterion.code = ActCode (not a concept domain, create new concept domain {ProcedureEventCriteriaProcedureType)
  • SubstanceAdministrationEventCriterion.code = ActCode (not a concept domain, create new concept domain SubstanceAdminEventCriteriaSubstanceAdministrationType)
  • ObservationEventCriterion.code = ActCode (not a concept domain, create new concept domain ObservationEventCriteriaObservationType)
  • Place.code = EntityCode (not a concept domain, use PlaceEntityType)

Resolution Items

  • Harm Proposal (Patrick aka PEL): Create new concept domains for SupplyType, OrderableSupplyType, ProcedureType, OrderableProcedureType, ActClassProcessStep, ActCodeProcessStep, OrderableObservationType, OrderableSubstanceAdministrationType