No Current Link To VocabularyCoded With ExtensionsCoded No Extensions
PORX_MT010120UV01
MedicationOrder

Derived from RMIM: PORX_RM010120UV01 and HMD: PORX_HD010120UV01
 
CombinedMedicationRequest

Design Comments: The CombinedMedicationRequest class captures information common to both the Substance Administration Request and/or the Supply Request. It will have one or more component relationships to other child orders, so that it acts as a grouper for them. This is an instance of the Header DMIM class.

UsageNotes: We need to bind code to a more appropriate concept domain.

classCode [1..1] (M)
Act (CS) {CNE:C:ActClass:ACT, fixed value= "ACT"}
moodCode [1..1] (M)
Act (CS) {CNE:V:ActMoodRequest, root= "RQO"}
id [0..*]
Act (DSET<II>)

Design Comments: A unique identifier for the order.

UsageNotes: For example this could be the prescription id for an order that has both a substance admin act and supply act.

code [0..1]
Act (CD) {CWE:D:ActSubstanceAdministrationCode}
text [0..1]
Act (ED)

Design Comments: A textual or multimedia description (or reference to a description) of the order.

statusCode [0..1]
Act (CS) {CNE:C:ActStatus:active, fixed value= "active"}

Design Comments: A code specifying the state of the order.

UsageNotes: For example, this may indicate that the Act is in an active or completed state

priorityCode [0..1]
Act (CD) {CWE:D:ActPriority}

Design Comments: A code (e.g. for routine, emergency), specifying the urgency under which the order is requested/demanded to happen.

confidentialityCode [0..1]
Act (CD) {CWE:D:Confidentiality}

Design Comments: A code that controls the disclosure of information about this order.

subject [0..1] (Subject5)

Design Comments: The patient that the medicine is intended for dispenses or introduced into/applied to for substance administrations.

directTarget [0..1] (DirectTarget)

Design Comments: Identifies the medication being prescribed.

recordTarget [0..1] (RecordTarget)

Design Comments: The record target indicates whose medical record holds the documentation of this order.

Rationale: This is especially important when the subject of the order is not the patient him/herself.

responsibleParty [0..1] (ResponsibleParty)

Design Comments: The person or organization that has primary responsibility for the order. The responsible party is not necessarily present in an action, but is accountable for the action through the power to delegate.

author [0..1] (Author3)

Design Comments: A party that originates the order and therefore has responsibility for the information given in the order.

transcriber [0..1] (DataEnterer2)

Design Comments: The party entering the data into the originating system.

verifier [0..*] (Verifier)

Design Comments: The person or organization that has primary responsibility for the order. The responsible party is not necessarily present in an action, but is accountable for the action through the power to delegate.

occurrenceOf [0..1] (OcurrenceOf)
definition [0..*] (Definition)

Design Comments: Enables the communication of a reference to a protocol, study or guideline.

predecessor [0..1] (Predecessor)

Design Comments: The order can be a renewal of a prior order.

replacementOf [0..*] (ReplacementOf)

Design Comments: The order can be a replacement of a prior order.

reason [0..*] (Reason)

Design Comments: Specifies the reason (indication) for authoring the order.

precondition [0..*] (Precondition)

Design Comments: In order for the order to be acted upon, certain verification events should take place.

reference [0..*] (Reference)
coverage [0..*] (Coverage)

Design Comments: The costs for an order may be covered by a plan or policy .

pertinentInformation [0..*] (PertinentInformation)

Design Comments: Specifies any pertinent information relevant to the order.

component1 [0..*] (Component4)

Design Comments: The SubstanceAdministrationRequest is a component of the overall order.

component2 [0..1] (Component2)

Design Comments: The dispense request is a component of the overall order.

component3 [0..*] (SourceOf)

Design Comments: Allows for nesting orders, eg. line items, in an overarching parent order.

component4 [0..1] (Component8)

Design Comments: Enables the indication of whether the prescription is ineligible for trial dispensing.

Rationale: Serves as reminder for dispenser that the prescription is not to be trial-filled. In some jurisdictions, the prescription must be so designated by the prescriber for the dispenser to do trial dispensing.

subjectOf1 [0..1] (Subject4)

Design Comments: An order can be the subject of a review.

subjectOf2 [0..*] (Subject2)

Design Comments: The order can be a subject of detected medication issues.

subjectOf3 [0..*] (Subject3)

Design Comments: The order can be a subject of annotations.

subjectOf4 [0..*] (Subject)

Design Comments: The order can be the subject of the permissions related to substitution.

UsageNotes: Not sending this association implies that substitution is allowed.

componentOf1 [0..1] (Component5)

Design Comments: Used to link an order to a specific encounter.

componentOf2 [0..*] (Component6)

Design Comments: Specifies that an order is part of a work list.

 
Subject5

Design Comments: The patient that the medicine is intended for dispenses or introduced into/applied to for substance administrations.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationTargetSubject, root= "SBJ"}
contextControlCode [0..1]
Participation (CS) {CNE:C:ContextControl:AP, fixed value= "AP"}
awarenessCode [0..1]
Participation (CD) {CWE:D:TargetAwareness}

Design Comments: A code specifying the extent to which the patient is aware of the order.

patient [1..1] (R_PatientUniversal)
 
DirectTarget

Design Comments: Identifies the medication being prescribed.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationTargetDirect, root= "DIR"}
orderableMedication [1..1] (R_OrderableMedicationUniversal)
 
RecordTarget

Design Comments: The record target indicates whose medical record holds the documentation of this order.

Rationale: This is especially important when the subject of the order is not the patient him/herself.

typeCode [1..1] (M)
ManagedParticipation (CS) {CNE:C:ParticipationType:RCT, fixed value= "RCT"}
contextControlCode [0..1]
ManagedParticipation (CS) {CNE:C:ContextControl:OP, fixed value= "OP"}
patient [1..1] (R_PatientUniversal)
 
ResponsibleParty

Design Comments: The person or organization that has primary responsibility for the order. The responsible party is not necessarily present in an action, but is accountable for the action through the power to delegate.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationResponsibleParty, root= "RESP"}
contextControlCode [0..1]
Participation (CS) {CNE:C:ContextControl:AP, fixed value= "AP"}
assignedEntity [1..1] (R_AssignedEntityUniversal)
 
Author3

Design Comments: A party that originates the order and therefore has responsibility for the information given in the order.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationAuthorOriginator, root= "AUT"}
contextControlCode [0..1]
Participation (CS) {CNE:C:ContextControl:AP, fixed value= "AP"}
noteText [0..1]
Participation (ED)

Design Comments: A textual or multimedia depiction of commentary related to the authoring of the order.

time [0..1]
Participation (TS)

Design Comments: A time stamp specifying the time that the author was involved in the order.

modeCode [0..1]
Participation (CD) {CWE:D:ParticipationMode}

Design Comments: A code specifying the method by which the order was authored.

Rationale: This is used to specify whether the information represented by the order was initially provided verbally, written, or electronically.

signatureCode [0..1]
Participation (CD) {CNE:D:ParticipationSignature}

Design Comments: A code specifying whether and how the author has attested his participation through a signature and or whether such a signature is needed.

signatureText [0..1]
Participation (ED)

Design Comments: A textual or multimedia depiction of the signature by which the author endorses his or her authoring of the order and that he or she agrees to assume the associated accountability.

assignedEntity [1..1] (R_AssignedEntityUniversal)
 
DataEnterer2

Design Comments: The party entering the data into the originating system.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationInformationTranscriber, root= "TRANS"}
contextControlCode [0..1]
Participation (CS) {CNE:C:ContextControl:AP, fixed value= "AP"}
noteText [0..1]
Participation (ED)

Design Comments: A textual or multimedia depiction of commentary related to the data entry.

time [0..1]
Participation (TS)

Design Comments: A time stamp specifying the time that the data enterer was involved in the order.

modeCode [0..1]
Participation (CD) {CWE:D:ParticipationMode}

Design Comments: A code specifying the method by which the order data was entered.

Rationale: This is used to specify whether the information represented by the order was initially provided verbally, written, or electronically.

signatureCode [0..1]
Participation (CD) {CNE:D:ParticipationSignature}

Design Comments: A code specifying whether and how the data enterer has attested his participation through a signature and or whether such a signature is needed.

signatureText [0..1]
Participation (ED)

Design Comments: A textual or multimedia depiction of the signature by which the data enterer endorses his or her entry of the order data and that he or she agrees to assume the associated accountability.

assignedEntity [1..1] (R_AssignedEntityUniversal)
 
Verifier

Design Comments: The person or organization that has primary responsibility for the order. The responsible party is not necessarily present in an action, but is accountable for the action through the power to delegate.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationVerifier, root= "VRF"}
functionCode [0..1]
Participation (CD) {CWE:D:ParticipationFunction}
contextControlCode [0..1]
Participation (CS) {CNE:C:ContextControl:AP, fixed value= "AP"}
noteText [0..1]
Participation (ED)
time [0..1]
Participation (TS)
modeCode [0..1]
Participation (CD) {CWE:D:ParticipationMode}
signatureCode [0..1]
Participation (CD) {CNE:D:ParticipationSignature}
signatureText [0..1]
Participation (ED)
assignedEntity [1..1] (R_AssignedEntityUniversal)
 
OcurrenceOf
typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipOccurrence, root= "OCCR"}
sequenceNumber [0..1]
ActRelationship (INT.NONNEG)
substanceAdministrationIntent [1..1] (SubstanceAdministrationIntent)
 
SubstanceAdministrationIntent
classCode [1..1] (M)
SubstanceAdministration (CS) {CNE:V:ActClassSubstanceAdministration, root= "SBADM"}
moodCode [1..1] (M)
SubstanceAdministration (CS) {CNE:V:ActMoodIntent, root= "INT"}
id [0..1]
SubstanceAdministration (II)
repeatNumber [0..1]
SubstanceAdministration (INT.NONNEG)
 
Definition

Design Comments: Enables the communication of a reference to a protocol, study or guideline.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipInstantiatesMaster, root= "INST"}
substanceAdministrationDefinition [1..1] (SubstanceAdministrationDefinition)

Design Comments: A protocol, study or guideline related to substance administrations.

 
SubstanceAdministrationDefinition

Design Comments: A protocol, study or guideline related to substance administrations.

classCode [1..1] (M)
SubstanceAdministration (CS) {CNE:V:ActClassSubstanceAdministration, root= "SBADM"}
moodCode [1..1] (M)
SubstanceAdministration (CS) {CNE:V:ActMoodDefinition, root= "DEF"}
id [1..1] (M)
SubstanceAdministration (II)

Design Comments: Unique identifier of the protocol, study, or guideline.

 
Predecessor

Design Comments: The order can be a renewal of a prior order.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipSucceeds, root= "SUCC"}
priorCombinedMedicationRequest [1..1] (PriorCombinedMedicationRequest2)

Design Comments: An order that is related to another order.

 
PriorCombinedMedicationRequest2

Design Comments: An order that is related to another order.

classCode [1..1] (M)
SubstanceAdministration (CS) {CNE:V:ActClassSubstanceAdministration, root= "SBADM"}
moodCode [1..1] (M)
SubstanceAdministration (CS) {CNE:V:ActMoodRequest, root= "RQO"}
id [1..1] (M)
SubstanceAdministration (II)

Design Comments: Unique identifier for the renewed order

 
ReplacementOf
[Constraint: "

Only present if interaction PORX_IN010410 is used. If the interaction PORX_IN010410 is used, then this association must be present.

"]

Design Comments: The order can be a replacement of a prior order.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipReplaces, root= "RPLC"}
priorCombinedMedicationRequest [1..1] (PriorCombinedMedicationRequest)

Design Comments: A order that has become obsolete as a result of being replaced by another order.

 
PriorCombinedMedicationRequest

Design Comments: A order that has become obsolete as a result of being replaced by another order.

classCode [1..1] (M)
SubstanceAdministration (CS) {CNE:V:ActClassSubstanceAdministration, root= "SBADM"}
moodCode [1..1] (M)
SubstanceAdministration (CS) {CNE:V:ActMoodRequest, root= "RQO"}
id [1..1] (M)
SubstanceAdministration (II)

Design Comments: Unique identifier for the obsoleted order.

statusCode [1..1] (M)
SubstanceAdministration (CS) {CNE:C:ActStatus:obsolete, fixed value= "obsolete"}
 
Reason

Design Comments: Specifies the reason (indication) for authoring the order.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipReason, root= "RSON"}
priorityNumber [0..1]
ActRelationship (INT)

Design Comments: Indiciates the priority of this reason for the order in relation to its sibling reasons.

clinicalStatement [1..1] (A_SupportingClinicalStatementMinimal)
 
Precondition

Design Comments: In order for the order to be acted upon, certain verification events should take place.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasPre-condition, root= "PRCN"}
verficationEventCriterion [1..1] (VerficationEventCriterion)
 
VerficationEventCriterion
classCode [1..1] (M)
Observation (CS) {CNE:V:ActClassVerification, root= "VERIF"}
moodCode [1..1] (M)
Observation (CS) {CNE:V:ActMoodEventCriterion, root= "EVN.CRT"}
code [0..1]
Observation (CD) {CWE:D:ActObservationVerificationType}
 
Reference
typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipRefersTo, root= "REFR"}
priorCombinedMedicationRequest [1..1] (PriorCombinedMedicationRequest2)
 
Coverage

Design Comments: The costs for an order may be covered by a plan or policy .

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipCoveredBy, root= "COVBY"}
coverage [1..1] (A_CoverageDeprecated)
 
PertinentInformation

Design Comments: Specifies any pertinent information relevant to the order.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipPertains, root= "PERT"}
clinicalStatement [1..1] (A_SupportingClinicalStatementMinimal)
 
Component4

Design Comments: The SubstanceAdministrationRequest is a component of the overall order.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasComponent, root= "COMP"}
sequenceNumber [0..1]
ActRelationship (INT.NONNEG)

Design Comments: Indicates the sequence of the SubstanceAdministrationRequests.

priorityNumber [0..1]
ActRelationship (INT)

Design Comments: Indicates the priority in the sequence of the SubstanceAdministrationRequest.

seperatableInd [0..1]
ActRelationship (BL){fixed value= "false"}
substanceAdministrationRequest [1..1] (SubstanceAdministrationRequest)

Design Comments: An act that involves introducing or otherwise applying a medicine into or to the subject.

UsageNotes: We need to bind code to a more appropriate concept domain.

 
SubstanceAdministrationRequest

Design Comments: An act that involves introducing or otherwise applying a medicine into or to the subject.

UsageNotes: We need to bind code to a more appropriate concept domain.

classCode [1..1] (M)
SubstanceAdministration (CS) {CNE:V:ActClassSubstanceAdministration, root= "SBADM"}
moodCode [1..1] (M)
SubstanceAdministration (CS) {CNE:V:ActMoodRequest, root= "RQO"}
id [0..*]
SubstanceAdministration (DSET<II>)

Design Comments: A unique identifier for the Substance Administration.

code [0..1]
SubstanceAdministration (CD) {CWE:D:ActCode}

Design Comments: Used to differentiate the type of SubstanceAdministration, eg. maintenance dose.

text [0..1]
SubstanceAdministration (ED)

Design Comments: A textual or multimedia description (or reference to a description) of the Substance Administration.

statusCode [0..1]
SubstanceAdministration (CS) {CNE:C:ActStatus:active, fixed value= "active"}
effectiveTime [0..1]
SubstanceAdministration (QSET<TS>)

Design Comments: Indicates the timing of the substance administration.

UsageNotes: Note that because a substance adminstration that may be describing an ongoing process that occurs at many points in time (e.g. "three times a day) within a time period (which may or may not be indefinite, e.g. "for 7 days", or "continuously"), the times associated with the administrations is often "nested".

repeatNumber [0..1]
SubstanceAdministration (IVL<INT.NONNEG>)

Design Comments: An interval of integer numbers stating the minimal and maximal number of repetitions of the Substance Administration.

independentInd [0..1]
SubstanceAdministration (BL)

Design Comments: An indicator specifying whether the substance administration can be manipulated independently of the order.

approachSiteCode [0..*]
SubstanceAdministration (DSET<CD>) {CWE:D:ActSite}

Design Comments: A coded specification of the anatomic site where the medication first enters the body.

routeCode [0..1]
SubstanceAdministration (CD) {CWE:D:RouteOfAdministration}

Design Comments: A code specifying the route or physiological path of administration of a therapeutic agent into or onto a subject.

doseQuantity [0..1]
SubstanceAdministration (URG<PQ>)

Design Comments: The amount of the therapeutic or other substance given at one administration event.

rateQuantity [0..1]
SubstanceAdministration (URG<PQ>)

Design Comments: Identifies the speed with which the substance is introduced into the subject.

doseCheckQuantity [0..*]
SubstanceAdministration (DSET<RTO<PQ,PQ.TIME>>)

Design Comments: This attribute identifies the expected quantity to be consumed over a period of time. It is used as a verification check on the values specified for other values.

maxDoseQuantity [0..*]
SubstanceAdministration (DSET<RTO<PQ,PQ.TIME>>)

Design Comments: Identifies the maximum total quantity of a therapeutic substance that my be administered to a subject over the period of time.

administrationUnitCode [0..1]
SubstanceAdministration (CD) {CWE:D:AdministrableDrugForm}

Design Comments: A code for the administered thing taken from a larger whole. Used if the consumable material is specified as a larger whole but the doseQuantity related to a specific portion of it rather than the entire consumable material.

device [0..*] (Device)

Design Comments: The device to be used when administering the medication.

consumable [0..1] (Consumable)

Design Comments: The medication that is being administered.

location [0..1] (Location1)

Design Comments: Indicates the intended location where the medication is to be administered.

goal [0..*] (Goal)

Design Comments: The desired outcome of the SubstanceAdministration, eg. keep systolic blood pressure between 90 and 110 mm Hg.

option [0..*] (Option)

Design Comments: A SubstanceAdministrationRequest may have relationships to other SubstanceAdministrationRequests that provide more detailed properties.

trigger [0..*] (Trigger)

Design Comments: A pre-condition that if true will result in the SubstanceAdministration being performed.

precondition [0..*] (Precondition2)

Design Comments: A requirement to be true before the SubstanceAdministration is performed.

component [0..*] (Component7)

Design Comments: Allows for the creation of complex Substance Administrations.

subjectOf [0..*] (Subject1)

Design Comments: The SubstanceAdministrationRequest can be the subject of annotations.

 
Device

Design Comments: The device to be used when administering the medication.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationTargetDevice, root= "DEV"}
choice [1..1] (Choice)
 
Choice
choice of Access

Design Comments: Indicates which access to use to administer the medication.

          or R_AssignedDeviceUniversal
 
Access

Design Comments: Indicates which access to use to administer the medication.

classCode [1..1] (M)
Access (CS) {CNE:V:RoleClassAccess, root= "ACCESS"}
id [0..1]
Access (II)

Design Comments: Unique id for specific access occurrences

name [0..1]
Access (ST)

Design Comments: The name of the access occurrence, eg. central line

accessDevice [0..1] (Device2)

Design Comments: The details of the device being used to administer the medication via the defined access.

 
Device2

Design Comments: The details of the device being used to administer the medication via the defined access.

classCode [1..1] (M)
Device (CS) {CNE:V:EntityClassDevice, root= "DEV"}
determinerCode [1..1] (M)
Device (CS) {CNE:V:EntityDeterminerSpecific, root= "INSTANCE"}
name [0..1]
Device (ST)

Design Comments: The name of the device being used to administer the medication via the defined access.

 
Consumable

Design Comments: The medication that is being administered.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationConsumable, root= "CSM"}
orderableMedication [1..1] (R_OrderableMedicationUniversal)
 
Location1

Design Comments: Indicates the intended location where the medication is to be administered.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationTargetLocation, root= "LOC"}
serviceDeliveryLocation [1..1] (R_ServiceDeliveryLocationUniversal)
 
Goal

Design Comments: The desired outcome of the SubstanceAdministration, eg. keep systolic blood pressure between 90 and 110 mm Hg.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipObjective}
conjunctionCode [0..1]
ActRelationship (CS) {CNE:V:RelationshipConjunction}

Design Comments: A code specifying the logical conjunction of the criteria.

observationEventCriterion [1..1] (ObservationEventCriterion)

Design Comments: An observation that must occur for the SubstanceAdministration to be considered.

 
ObservationEventCriterion

Design Comments: An observation that must occur for the SubstanceAdministration to be considered.

classCode [1..1] (M)
Observation (CS) {CNE:V:ActClassObservation, root= "OBS"}
moodCode [1..1] (M)
Observation (CS) {CNE:V:ActMoodEventCriterion, root= "EVN.CRT"}
code [0..1]
Observation (CD) {CWE:D:ActCode}

Design Comments: Indicates the type of measurable patient or medication characteristic being expressed.

Rationale: Needed to identify what type of characteristic is being expressed.

actionNegationInd [0..1]
Observation (BL)

Design Comments: If true, indicates that the characteristic is one which should *not* be held

text [0..1]
Observation (ED)

Design Comments: A textual or multimedia depiction of commentary related to the observation.

effectiveTime [0..1]
Observation (IVL<TS>)

Design Comments: Indicates the time period over which the critera must be observed.

value [0..1]
Observation (ANY) {CWE:D:ObservationValue}

Design Comments: Indicates the specific value or range of the characteristic.

 
Option

Design Comments: A SubstanceAdministrationRequest may have relationships to other SubstanceAdministrationRequests that provide more detailed properties.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasOption, root= "OPTN"}
priorityNumber [0..1]
ActRelationship (INT)

Design Comments: Used to indicate the priority of the SubstanceAdministrationRequests.

substanceAdministrationRequest [1..1] (SubstanceAdministrationRequest)
 
Trigger

Design Comments: A pre-condition that if true will result in the SubstanceAdministration being performed.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasTrigger, root= "TRIG"}
pauseQuantity [0..1]
ActRelationship (PQ.TIME)

Design Comments: A quantity of time that should elapse between when the criteria is true and the substance administration.

checkpointCode [0..1]
ActRelationship (CS) {CNE:V:ActRelationshipCheckpoint}

Design Comments: A code specifying when in the course of the substance administration, a trigger for the adminstration is evaluated.

conjunctionCode [0..1]
ActRelationship (CS) {CNE:V:RelationshipConjunction}

Design Comments: A code specifying the logical conjunction of the criteria.

criteriaChoice [1..1] (CriteriaChoice)
 
Precondition2

Design Comments: A requirement to be true before the SubstanceAdministration is performed.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasPre-condition, root= "PRCN"}
pauseQuantity [0..1]
ActRelationship (PQ.TIME)

Design Comments: A quantity of time that should elapse between when the criteria is true and the substance administration.

checkpointCode [0..1]
ActRelationship (CS) {CNE:V:ActRelationshipCheckpoint}

Design Comments: A code specifying when in the course of the substance administration a precondition for the administration is evaluated.

conjunctionCode [0..1]
ActRelationship (CS) {CNE:V:RelationshipConjunction}

Design Comments: A code specifying the logical conjunction of the criteria.

criteriaChoice [1..1] (CriteriaChoice)
 
CriteriaChoice
choice of ProcedureEventCriterion

Design Comments: A procedure that must occur for the SubstanceAdministration to be considered.

          or SubsAdminEventCriterion

Design Comments: A criteria that involves introducing or otherwise applying a medicine into or to the subject.

UsageNotes: To allow current medication to depend on another

          or ObservationEventCriterion

Design Comments: An observation that must occur for the SubstanceAdministration to be considered.

 
ProcedureEventCriterion

Design Comments: A procedure that must occur for the SubstanceAdministration to be considered.

classCode [1..1] (M)
Procedure (CS) {CNE:V:ActClassProcedure, root= "PROC"}
moodCode [1..1] (M)
Procedure (CS) {CNE:V:ActMoodEventCriterion, root= "EVN.CRT"}
id [0..1]
Procedure (II)

Design Comments: Unique id for procedure event criteria.

code [0..1]
Procedure (CD) {CWE:D:ActCode}

Design Comments: A code specifying the particular kind of Procedure.

actionNegationInd [0..1]
Procedure (BL)

Design Comments: If true, indicates that the procedure should not have been performed.

text [0..1]
Procedure (ED)

Design Comments: A textual or multimedia depiction of commentary related to the participation.

effectiveTime [0..1]
Procedure (QSET<TS>)

Design Comments: The timing related to the procedure.

 
SubsAdminEventCriterion

Design Comments: A criteria that involves introducing or otherwise applying a medicine into or to the subject.

UsageNotes: To allow current medication to depend on another

classCode [1..1] (M)
SubstanceAdministration (CS) {CNE:C:ActClass:SBADM, fixed value= "SBADM"}
moodCode [1..1] (M)
SubstanceAdministration (CS) {CNE:C:ActMood:EVN.CRT, fixed value= "EVN.CRT"}
id [0..1]
SubstanceAdministration (II)

Design Comments: A unique identifier for the Substance Administration.

code [0..1]
SubstanceAdministration (CD) {CWE:D:ActCode}

Design Comments: A code specifying the particular kind of Substance Administration.

actionNegationInd [0..1]
SubstanceAdministration (BL)

Design Comments: If true, indicates that the SubstanceAdministration has not been administered.

text [0..1]
SubstanceAdministration (ED)

Design Comments: A textual or multimedia description (or reference to a description) of the Substance Administration.

effectiveTime [0..1]
SubstanceAdministration (QSET<TS>)

Design Comments: Indicates the timing of the substance administration.

doseQuantity [0..1]
SubstanceAdministration (URG<PQ>)

Design Comments: The amount of the therapeutic or other substance given at one administration event

consumable [1..1] (Consumable2)

Design Comments: The medication that was intended to be administered.

 
Consumable2

Design Comments: The medication that was intended to be administered.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationConsumable, root= "CSM"}
administerableMedication [1..1] (R_AdministerableMedicationUniversal)
 
Component7

Design Comments: Allows for the creation of complex Substance Administrations.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasComponent, root= "COMP"}
sequenceNumber [1..1] (M)
ActRelationship (INT.NONNEG)

Design Comments: Indicates the priority in the sequence of the Substance Administrations.

substanceAdministrationRequest [1..1] (SubstanceAdministrationRequest)
 
Subject1

Design Comments: The SubstanceAdministrationRequest can be the subject of annotations.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasSubject, root= "SUBJ"}
annotation [1..1] (A_AnnotationUniversal)
 
Component2

Design Comments: The dispense request is a component of the overall order.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasComponent, root= "COMP"}
seperatableInd [0..1]
ActRelationship (BL){fixed value= "false"}
dispenseRequest [1..1] (DispenseRequest)

Design Comments: An act that involves provision of a medicine.

 
DispenseRequest

Design Comments: An act that involves provision of a medicine.

classCode [1..1] (M)
Supply (CS) {CNE:V:ActClassSupply, root= "SPLY"}
moodCode [1..1] (M)
Supply (CS) {CNE:V:ActMoodRequest, root= "RQO"}
id [0..*]
Supply (DSET<II>)

Design Comments: Unique identifiers for the Dispense.

code [0..1]
Supply (CD) {CNE:D:ActPharmacySupplyType}

Design Comments: A code specifying the particular type of Dispense, eg. First Fill.

text [0..1]
Supply (ED)

Design Comments: A textual or multimedia description (or reference to a description) of the Dispense.

statusCode [0..1]
Supply (CS) {CNE:C:ActStatus:active, fixed value= "active"}

Design Comments: A code specifying the state of the Dispense.

UsageNotes: For example, this may indicate that the Dispense is in an active or completed state

effectiveTime [0..1]
Supply (QSET<TS>)

Design Comments: This indicates the validity period of a prescription (stale dating the Prescription)

It reflects the prescriber perspective for the validity of the prescription. Dispenses must not be made against the prescription outside of this period. The lower-bound of the Dispensing Window signifies the earliest date that the prescription can be filled for the first time. If an upper-bound is not specified then the Prescription is open-ended or will default to a stale-date based on regulations.

Rationale: Indicates when the Prescription becomes valid, and when it ceases to be a dispensable Prescription.

repeatNumber [0..1]
Supply (INT.NONNEG){default= "1"}

Design Comments: An integer indicating the number of repeats of the Dispense.

UsageNotes: For example, the number of times the prescribed quantity is to be supplied including the initial standard fill.

independentInd [0..1]
Supply (BL)

Design Comments: An indicator specifying whether the Dispense can be handled independently of the order.

quantity [1..1]
Supply (PQ)

Design Comments: The amount that is to be dispensed.

expectedUseTime [0..1]
Supply (IVL<TS>)

Design Comments: Identifies the period time over which the supplied product is expected to be used, or the length of time the dispense is expected to last.

UsageNotes: In some situations, this attribute may be used instead of quantity to identify the amount supplied by how long it is expected to last, rather than the physical quantity issued. E.g. 90 days supply of medication (based on an ordered dosage) NOTE: When possible, it is always better to specify quantity, as this tends to be more precise. ExpectedUseTime will always be an estimate that can be influenced by external factors.

product [0..1] (Product)

Design Comments: Identifies the medication to be dispensed.

receiver [0..*] (Receiver)

Design Comments: Identifies a person(s), other than the patient, who are authorized to pickup the medication.

performer [0..1] (Performer)

Design Comments: Identifies the organization that is intended to perform the dispense.

origin [0..1] (Origin)
destination [0..1] (Destination)

Design Comments: Identifies the location where the dispensed medication is to be delivered after being prepared.

location [0..1] (Location2)

Design Comments: Identifies the location to which the order has been directed for preparation.

component [0..*] (Component3)

Design Comments: Allows for the creation of complex dispense requests.

subjectOf [0..*] (Subject6)

Design Comments: The DispenseRequest can be a subject of annotations.

 
Product

Design Comments: Identifies the medication to be dispensed.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationProduct, root= "PRD"}
administerableMedication [1..1] (R_AdministerableMedicationUniversal)
 
Receiver

Design Comments: Identifies a person(s), other than the patient, who are authorized to pickup the medication.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationReceiver, root= "RCV"}
assignedPerson [1..1] (R_AssignedPersonUniversal)
 
Performer

Design Comments: Identifies the organization that is intended to perform the dispense.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationPhysicalPerformer, root= "PRF"}
substitutionConditionCode [0..1]
Participation (CD) {CWE:D:SubstitutionCondition}

Design Comments: This indicates whether the author will allow the dispense to be performed by a different organization.

assignedOrganization [1..1] (R_AssignedOrganizationUniversal)
 
Origin
typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationOrigin, root= "ORG"}
serviceDeliveryLocation [1..1] (R_ServiceDeliveryLocationUniversal)
 
Destination

Design Comments: Identifies the location where the dispensed medication is to be delivered after being prepared.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationDestination, root= "DST"}
serviceDeliveryLocation [1..1] (R_ServiceDeliveryLocationUniversal)
 
Location2

Design Comments: Identifies the location to which the order has been directed for preparation.

typeCode [1..1] (M)
Participation (CS) {CNE:C:ParticipationType:LOC, fixed value= "LOC"}
time [0..1]
Participation (IVL<TS>)

Design Comments: The time when the patient is expected to pickup the medication.

substitutionConditionCode [0..1]
Participation (CV) {CNE:V:x_SubstitutionConditionNoneOrUnconditional}

Design Comments: Indicates whether the author will allow the dispense to be prepared at a different location.

serviceDeliveryLocation [1..1] (R_ServiceDeliveryLocationUniversal)
 
Component3

Design Comments: Allows for the creation of complex dispense requests.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasComponent, root= "COMP"}
sequenceNumber [1..1] (M)
ActRelationship (INT.NONNEG)

Design Comments: Indicates the sequence of the related dispense requests.

dispenseRequest [1..1] (DispenseRequest)
 
Subject6

Design Comments: The DispenseRequest can be a subject of annotations.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasSubject, root= "SUBJ"}
annotation [1..1] (A_AnnotationUniversal)
 
SourceOf

Design Comments: Allows for nesting orders, eg. line items, in an overarching parent order.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:C:ActRelationshipType:COMP, fixed value= "COMP"}
sequenceNumber [0..1]
ActRelationship (INT.NONNEG)

Design Comments: Indicates the sequence of this order.

combinedMedicationRequest [1..1] (CombinedMedicationRequest)
 
Component8

Design Comments: Enables the indication of whether the prescription is ineligible for trial dispensing.

Rationale: Serves as reminder for dispenser that the prescription is not to be trial-filled. In some jurisdictions, the prescription must be so designated by the prescriber for the dispenser to do trial dispensing.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:C:ActRelationshipType:COMP, fixed value= "COMP"}
negationInd [1..1] (M)
ActRelationship (BL)
trialSupplyPermission [1..1] (TrialSupplyPermission)
 
TrialSupplyPermission
classCode [1..1] (M)
Supply (CS) {CNE:C:ActClass:SPLY, fixed value= "SPLY"}
moodCode [1..1] (M)
Supply (CS) {CNE:C:ActMood:PERM, fixed value= "PERM"}
code [1..1]
Supply (CV) {CNE:C:ActCode:TF, fixed value= "TF"}

Design Comments: Fixed to Trial Fill

 
Subject4

Design Comments: An order can be the subject of a review.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasSubject, root= "SUBJ"}
review [1..1] (Review)

Design Comments: The details of a Review that is associated with the order.

 
Review

Design Comments: The details of a Review that is associated with the order.

classCode [1..1] (M)
Act (CS) {CNE:V:ActClassReview, root= "REV"}
moodCode [1..1] (M)
Act (CS) {CNE:V:x_ActMoodDefEvnRqoPrmsPrp}

Design Comments: Indicates the mood of the Review association, eg. whether the review has already taken, whether it is being requested to take place.

id [0..1]
Act (II)

Design Comments: Unique id for the review

effectiveTime [0..1]
Act (TS)

Design Comments: The time associated with this Review. For a Review in RQO mood, this would be the time when the author has requested the review take place.

 
Subject2

Design Comments: The order can be a subject of detected medication issues.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasSubject, root= "SUBJ"}
detectedMedicationIssue [1..1] (A_DetectedMedicationIssueUniversal)
 
Subject3

Design Comments: The order can be a subject of annotations.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasSubject, root= "SUBJ"}
annotation [1..1] (A_AnnotationUniversal)
 
Subject

Design Comments: The order can be the subject of the permissions related to substitution.

UsageNotes: Not sending this association implies that substitution is allowed.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasSubject, root= "SUBJ"}
substitutionPermission [1..1] (SubstitutionPermission)

Design Comments: The permissions related to substitution on an order.

 
SubstitutionPermission

Design Comments: The permissions related to substitution on an order.

classCode [1..1] (M)
Act (CS) {CNE:V:ActClassSubstitution, root= "SUBST"}
moodCode [1..1] (M)
Act (CS) {CNE:V:ActMoodPermission, root= "PERM"}
code [1..1] (M)
Act (CD) {CNE:D:ActSubstanceAdminSubstitutionCode}

Design Comments: The type of substitution that this permission relates to.

actionNegationInd [0..1]
Act (BL){default= "false"}

Design Comments: Used to convey that the specified type of substitution is not allowed.

reasonCode [0..*]
Act (DSET<CD>) {CWE:V:SubstanceAdminSubstitutionNotAllowedReason}

Design Comments: Used when substitution is not allowed and indicates the reason for why substitution is not allowed.

 
Component5

Design Comments: Used to link an order to a specific encounter.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasComponent, root= "COMP"}
encounter [1..1] (A_EncounterUniversal)
 
Component6

Design Comments: Specifies that an order is part of a work list.

typeCode [1..1] (M)
ActRelationship (CS) {CNE:V:ActRelationshipHasComponent, root= "COMP"}
workingList [1..1] (WorkingList)

Design Comments: A means of grouping orders to reflect the needs of an individual worker, team of workers, or an organization.

 
WorkingList

Design Comments: A means of grouping orders to reflect the needs of an individual worker, team of workers, or an organization.

classCode [1..1] (M)
WorkingList (CS) {CNE:V:ActClassWorkingList, root= "LIST"}
moodCode [1..1] (M)
WorkingList (CS) {CNE:V:ActMoodEventOccurrence, root= "EVN"}
id [0..*]
WorkingList (DSET<II>)

Design Comments: Unique set of ids for the worklist.

code [0..1]
WorkingList (CD) {CWE:V:ActListCode}

Design Comments: A classification for the type of worklist.