Union of http://hl7.org/cda/us/ccda/StructureDefinition/PlannedSupply and http://hl7.org/cda/us/ccda/StructureDefinition/PlannedSupply

This is the set of resources that conform to either of the profiles Planned Supply (http://hl7.org/cda/us/ccda/StructureDefinition/PlannedSupply) and Planned Supply (http://hl7.org/cda/us/ccda/StructureDefinition/PlannedSupply). E.g. what you have to deal with if you get resources conforming to one of them

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Supply C1..1Base for all types and resources
Constraints: should-text-ref-value, should-effectiveTime, shall-product-or-device, should-author
... 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 0..1CDBinding: ?? (example)
... 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..1TELConstraints: value-starts-octothorpe
.... thumbnail 0..1ED
... statusCode 1..1CSBinding: ?? (required)
.... nullFlavor 0..1??Binding: ?? (required)
.... code 1..1??
.... sdtcValueSet 0..1??
.... sdtcValueSetVersion 0..1??
... effectiveTime 0..1The effectiveTime in a planned supply represents the time that the supply should occur.
.... effectiveTimeSXCM_TS
.... effectiveTimeIVL_TS
.... effectiveTimeEIVL_TS
.... effectiveTimePIVL_TS
.... effectiveTimeSXPR_TS
... priorityCode 0..*CEBinding: ?? (example)
... repeatNumber 0..1IVL_INTIn a Planned Supply, repeatNumber indicates the number of times the supply event can occur. For example, if a medication is filled at a pharmacy and the prescription may be refilled 3 more times, the supply RepeatNumber equals 4.
... independentInd 0..1BL
... quantity 0..1PQ
... expectedUseTime 0..1IVL_TS
... product 0..1InfrastructureRootRepresents either a medication or an immunization supply
.... 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 1..1??, ??Base for all types and resources
... subject 0..1Subject
... specimen 0..*Specimen
... performer 0..*Performer2The clinician who is expected to perform the supply could be identified using supply/performer.
... author 0..1??The author in a supply represents the clinician who is requesting or planning the supply.
... informant 0..*Informant
... participant 0..*Participant2This participant represents a device that is ordered, requested or intended for the patient.
... entryRelationship 0..*EntryRelationshipThe following entryRelationship represents the insurance coverage the patient may have for the supply.
... reference 0..*Reference
... precondition 0..*Precondition
... sdtcInFulfillmentOf1 0..*InFulfillmentOf1

doco Documentation for this format