Intersection of http://hl7.org/cda/us/ccda/StructureDefinition/MedicationDispense and http://hl7.org/cda/us/ccda/StructureDefinition/MedicationDispense

This is the set of resources that conform to both Medication Dispense (http://hl7.org/cda/us/ccda/StructureDefinition/MedicationDispense) and Medication Dispense (http://hl7.org/cda/us/ccda/StructureDefinition/MedicationDispense).

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Supply C1..1Base for all types and resources
should-text-ref-value: SHOULD contain text/reference/@value
should-effectiveTime: SHOULD contain effectiveTime
should-repeatNumber: SHOULD contain repeatNumber
should-quantity: SHOULD contain quantity
... nullFlavor 0..1??, ??Binding: ?? (required)
... realmCode 0..*CS
... typeId 0..1II
.... nullFlavor 0..1??, ??Binding: ?? (required)
.... assigningAuthorityName 0..1??, ??
.... displayable 0..1??, ??
.... root 1..1??, ??, ??, ??
.... extension 1..1??, ??
... classCode 1..1??, ??Binding: ?? (required)
... moodCode 1..1??, ??Binding: ?? (required)
... code 1..1CDleft: The CDA base standard limits codes that can be used at CDA supply.statusCode. In C-CDA, the Supply.code value set re-uses the value set used in FHIR and FHIR US Core MedicationDispense @ MedicationDispense.status and fixes statsuCode to 'completed'.; right: The CDA base standard limits codes that can be used at CDA supply.statusCode which do not represent typical medication dispense statuses. In order to provide correct domain vocabulary and align with FHIR, CDA supply.statusCode is fixed to completed and the FHIR MedicationDispense status value set is used at supply.code.
Binding: ?? (required)
... text 0..1EDSHOULD reference the portion of section narrative text corresponding to this entry
.... nullFlavor 0..1??, ??Binding: ?? (required)
.... compression 0..1??, ??Binding: ?? (required)
.... integrityCheck 0..1??, ??
.... integrityCheckAlgorithm 0..1??, ??Binding: ?? (required)
.... language 0..1??, ??
.... mediaType 0..1??, ??Binding: ?? (example)
.... representation 0..1??, ??Binding: ?? (required)
.... xmlText 0..1??, ??Allows for mixed text content. If @representation='B64', this SHALL be a base64binary string.
.... reference C0..1TELvalue-starts-octothorpe: If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative
.... thumbnail 0..1ED
... statusCode 1..1CSBinding: ?? (required)
.... nullFlavor 0..1??, ??Binding: ?? (required)
.... code 1..1??, ??
.... sdtcValueSet 0..1??, ??
.... sdtcValueSetVersion 0..1??, ??
... effectiveTime 0..1
.... effectiveTimeSXCM_TS
.... effectiveTimeIVL_TS
.... effectiveTimeEIVL_TS
.... effectiveTimePIVL_TS
.... effectiveTimeSXPR_TS
... priorityCode 0..*CEBinding: ?? (example)
... repeatNumber 0..1IVL_INTIn "EVN" (event) mood, the repeatNumber is the number of dispenses. For example, a repeatNumber of "3" indicates the third dispense.
... independentInd 0..1BL
... quantity 0..1PQ
... expectedUseTime 0..1IVL_TS
... product 1..1InfrastructureRoot
.... nullFlavor 0..1??, ??Binding: ?? (required)
.... realmCode 0..*CS
.... typeId 0..1II
..... nullFlavor 0..1??, ??Binding: ?? (required)
..... assigningAuthorityName 0..1??, ??
..... displayable 0..1??, ??
..... root 1..1??, ??, ??, ??
..... extension 1..1??, ??
.... templateId 0..*II
.... typeCode 0..1??, ??Binding: ?? (required)
.... manufacturedProduct C1..1??, ??, ??Base for all types and resources
product-choice: manufacturedLabeledDrug and manufacturedMaterial are mutually exclusive (one must be present)
... subject 0..1Subject
... specimen 0..*Specimen
... performer 0..1Performer2
.... nullFlavor 0..1??, ??Binding: ?? (required)
.... realmCode 0..*CS
.... typeId 0..1II
..... nullFlavor 0..1??, ??Binding: ?? (required)
..... assigningAuthorityName 0..1??, ??
..... displayable 0..1??, ??
..... root 1..1??, ??, ??, ??
..... extension 1..1??, ??
.... templateId 0..*II
.... typeCode 0..1??, ??Binding: ?? (required)
.... sdtcFunctionCode 0..1CE
.... time 0..1IVL_TS
.... modeCode 0..1CE
.... assignedEntity C1..1AssignedEntityshould-addr: SHOULD contain addr
..... nullFlavor 0..1??, ??Binding: ?? (required)
..... realmCode 0..*CS
..... typeId 0..1II
...... nullFlavor 0..1??, ??Binding: ?? (required)
...... assigningAuthorityName 0..1??, ??
...... displayable 0..1??, ??
...... root 1..1??, ??, ??, ??
...... extension 1..1??, ??
..... templateId 0..*II
..... classCode 0..1??, ??Binding: ?? (required)
..... sdtcIdentifiedBy 0..*IdentifiedBy
..... code 0..1CEBinding: ?? (example)
..... addr C0..1??, ??Base for all types and resources
shall-city: SHALL contain exactly one [1..1] city (CONF:81-7292).
shall-streetAddressLine: SHALL contain at least one and not more than 4 streetAddressLine (CONF:81-7291).
should-use: SHOULD contain @use
should-country: SHOULD contain country
81-7296: **SHALL NOT** have mixed content except for white space (CONF:81-7296)
81-10024: If the country is US, the state element is required and SHALL be selected from ValueSet StateValueSet but SHOULD have @nullFlavor if the state is unknown. If country is not specified, it's assumed to be US. If country is something other than US, the state MAY be present but MAY be bound to different vocabularies (CONF:81-10024).
81-10025: If the country is US, the postalCode element is required but SHOULD have @nullFlavor if the postalCode is unknown. If country is not specified, it's assumed to be US. If country is something other than US, the postalCode MAY be present but MAY be bound to different vocabularies (CONF:81-10025).
shall-max-ad-parts: SHALL have at most one of each: state, city, postalCode, and country
..... telecom 0..*TEL
..... assignedPerson 0..1Person
..... representedOrganization 0..1Organization
..... sdtcPatient 0..1Base
... author 0..*Author
... informant 0..*Informant
... participant 0..*Participant2
... entryRelationship 0..*EntryRelationship
... reference 0..*Reference
... precondition 0..*Precondition
... sdtcInFulfillmentOf1 0..*InFulfillmentOf1

doco Documentation for this format