This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Open Composite Order Vocab Items"

From HL7Wiki
Jump to navigation Jump to search
 
(3 intermediate revisions by one other user not shown)
Line 4: Line 4:
  
 
= 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 (PEL) = ActCode (not a concept domain, need to create a new concept GrouperType parent domain)
−
*Procedure.code (PEL) = ObservationType (incorrect binding domain, create new OrderableProcedureType domain under ActProcedureCode)
+
*Observation.code (PEL) = ObservationType (create new OrderableObservationType domain under ObservationType)
−
*Procedure.methodCode = ObservationMethod (incorrect binding domain, create a new ProcedureMethod domain)
+
*Procedure.code (PEL) = ObservationType (incorrect binding domain, create new OrderableProcedureCode domain under ActProcedureCode)
−
*Supply.code (PEL) = ObservationType (incorrect binding domain, create new ActSupplyType and OrderableSupplyType domain)
+
*Procedure.methodCode (RRH) = ObservationMethod (incorrect binding domain, create a new ProcedureMethod 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)
+
*Supply.code (PEL) = ObservationType (incorrect binding domain, create new SupplyType parent domain)
−
*Author.signatureCode = ParticipationSignature (do we really understand the usage here?)
+
*Substance Administration.code (PEL) = ActCode (not a concept domain, use ActSubstanceAdministrationCode)
−
*Consultant.functionCode = ParticipationFunction (concept domain too broad, need sub domain)
+
*Consultant.functionCode (RRH) = ParticipationFunction (concept domain too broad, need sub domain)
−
*Performer.functionCode = ParticipationFunction (concept domain too broad, need sub domain)
+
*Performer.functionCode (RRH) = ParticipationFunction (concept domain too broad, need sub domain)
 
*ProcessStep.classCode (PEL) = ActClassProcessStep (create new value set)
 
*ProcessStep.classCode (PEL) = ActClassProcessStep (create new value set)
 
*ProcessStep.code (PEL) = ActCodeProcessStep (create new concept domain)
 
*ProcessStep.code (PEL) = ActCodeProcessStep (create new concept domain)
−
*ParentRequestReference.classCode = ActClassCompositeOrder (create new value set)
+
*ParentRequestReference.classCode (PEL) = ActClassCompositeOrder (create new value set)
−
*PriorActRequest.classCode = ActClassCompositeOrder (create new value set)
+
*PriorActRequest.classCode (PEL) = ActClassCompositeOrder (create new value set)
−
*ProcedureEventCriterion.code = ActCode (not a concept domain, create new concept domain {ProcedureEventCriteriaProcedureType)
+
*ProcedureEventCriterion.code (PEL) = ActCode (not a concept domain, create new concept domain {ProcedureEventCriteriaType)
−
*SubstanceAdministrationEventCriterion.code = ActCode (not a concept domain, create new concept domain SubstanceAdminEventCriteriaSubstanceAdministrationType)
+
*SubstanceAdministrationEventCriterion.code (PEL) = ActCode (not a concept domain, create new concept domain SubstanceAdministrationEventCriteriaType)
−
*ObservationEventCriterion.code = ActCode (not a concept domain, create new concept domain ObservationEventCriteriaObservationType)
+
*ObservationEventCriterion.code (PEL) = ActCode (not a concept domain, create new concept domain ObservationEventCriteriaType)
−
*Place.code = EntityCode (not a concept domain, use PlaceEntityType)
+
*Place.code (RRH) = EntityCode (not a concept domain, use PlaceEntityType)
  
 
= Resolution Items =
 
= Resolution Items =
−
* Harm Proposal (Patrick aka PEL): Create new concept domains for SupplyType, OrderableSupplyType, ProcedureType, OrderableProcedureType, ActClassProcessStep, ActCodeProcessStep, OrderableObservationType, OrderableSubstanceAdministrationType
+
* Harm Proposal OO-200904-1 (Patrick aka PEL): Create new concept domains for GrouperType, SupplyType, OrderableProcedureType, OrderableObservationType, ResultableObservationType
 +
* Harm Proposal OO-200904-2 (PEL): Create new process step value sets ActClassProcessStep, ActCodeProcessStep
 +
* Harm Proposal OO-200904-3 (PEL): Create new criteria concept domains

Latest revision as of 15:44, 19 February 2009

Back to Orders & Observations WG main page

Back to Composite Order page

Vocabulary Items for Composite Order

  • PlacerGroup.code (PEL) = ActCode (not a concept domain, need to create a new concept GrouperType parent domain)
  • Observation.code (PEL) = ObservationType (create new OrderableObservationType domain under ObservationType)
  • Procedure.code (PEL) = ObservationType (incorrect binding domain, create new OrderableProcedureCode domain under ActProcedureCode)
  • Procedure.methodCode (RRH) = ObservationMethod (incorrect binding domain, create a new ProcedureMethod domain)
  • Supply.code (PEL) = ObservationType (incorrect binding domain, create new SupplyType parent domain)
  • Substance Administration.code (PEL) = ActCode (not a concept domain, use ActSubstanceAdministrationCode)
  • Consultant.functionCode (RRH) = ParticipationFunction (concept domain too broad, need sub domain)
  • Performer.functionCode (RRH) = 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 (PEL) = ActClassCompositeOrder (create new value set)
  • PriorActRequest.classCode (PEL) = ActClassCompositeOrder (create new value set)
  • ProcedureEventCriterion.code (PEL) = ActCode (not a concept domain, create new concept domain {ProcedureEventCriteriaType)
  • SubstanceAdministrationEventCriterion.code (PEL) = ActCode (not a concept domain, create new concept domain SubstanceAdministrationEventCriteriaType)
  • ObservationEventCriterion.code (PEL) = ActCode (not a concept domain, create new concept domain ObservationEventCriteriaType)
  • Place.code (RRH) = EntityCode (not a concept domain, use PlaceEntityType)

Resolution Items

  • Harm Proposal OO-200904-1 (Patrick aka PEL): Create new concept domains for GrouperType, SupplyType, OrderableProcedureType, OrderableObservationType, ResultableObservationType
  • Harm Proposal OO-200904-2 (PEL): Create new process step value sets ActClassProcessStep, ActCodeProcessStep
  • Harm Proposal OO-200904-3 (PEL): Create new criteria concept domains
Retrieved from "https://wiki.hl7.org/w/index.php?title=Open_Composite_Order_Vocab_Items&oldid=23147"