Union of https://dhp.uz/fhir/core/StructureDefinition/uz-core-provenance and https://dhp.uz/fhir/core/StructureDefinition/uz-core-provenance

This is the set of resources that conform to either of the profiles UZ Core Provenance (https://dhp.uz/fhir/core/StructureDefinition/uz-core-provenance) and UZ Core Provenance (https://dhp.uz/fhir/core/StructureDefinition/uz-core-provenance). E.g. what you have to deal with if you get resources conforming to one of them

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Provenance 0..*Who, What, When for a set of resources
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: ?? (required): IETF language tag for a human language
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
Constraints: ext-1
... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
Constraints: ext-1
... target SΣ1..*Reference(UZ Core Medication(0.9.0) | DocumentReference | #sd-857-uz-core-medication-uz-core-medication)Target Reference(s) (usually version specific)
... occurred[x] 0..1When the activity occurred
.... occurredPeriodPeriod
.... occurredDateTimedateTime
... recorded Σ0..1instantWhen the activity was recorded / updated
... policy 0..*uriPolicy or plan the activity was defined by
... location 0..1Reference(Location)Where the activity occurred, if relevant
... authorization 0..*CodeableReference()Authorization (purposeOfUse) related to the event
Binding: ?? (example): The authorized purposeOfUse for the activity.
... activity S0..1CodeableConceptActivity that occurred
Binding: ?? (required)
... basedOn 0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest | Task)Workflow authorization within which this event occurred
... patient S0..1Reference(Patient)The patient is the subject of the data created/updated (.target) by the activity
... encounter 0..1Reference(Encounter)Encounter within which this event occurred or which the event is tightly associated
... agent SΣC1..*BackboneElementActor involved
Constraints: prov-1, prov-2, prov-3
.... extension 0..*ExtensionAdditional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... type SΣ0..1CodeableConceptHow the agent participated
Binding: ?? (required)
.... role 0..*CodeableConceptWhat the agents role was
Binding: ?? (example): The role that a provenance agent played with respect to the activity.
.... who SΣ1..1Reference(UZ Core PractitionerRole(0.9.0) | #sd-898-uz-core-practitioner-role-uz-core-practitioner-role)The agent that participated in the event
.... onBehalfOf 0..1Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient)The agent that delegated
... entity SΣ0..*BackboneElementAn entity used in this activity
.... extension 0..*ExtensionAdditional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... role SΣ1..1coderevision | quotation | source | instantiates | removal
Binding: ?? (required)
.... what SΣ1..1Reference(Resource)Identity of entity
.... agent 0..*Entity is attributed to this agent
... signature S0..*SignatureSignature on target
.... extension 0..*ExtensionAdditional content defined by implementations
Constraints: ext-1
.... type SΣ1..*CodingIndication of the reason the entity signed the object(s)
Binding: ?? (preferred): An indication of the reason that an entity signed the object.
.... when SΣ0..1instantWhen the signature was created
.... who SΣ0..1Reference(UZ Core PractitionerRole(0.9.0) | #sd-898-uz-core-practitioner-role-uz-core-practitioner-role)Who signed
.... onBehalfOf Σ0..1Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization)The party represented
.... targetFormat 0..1codeThe technical format of the signed resources
Binding: ?? (required): BCP 13 (RFCs 2045, 2046, 2047, 4288, 4289 and 2049)
.... sigFormat S0..1codeThe technical format of the signature
Binding: ?? (required): BCP 13 (RFCs 2045, 2046, 2047, 4288, 4289 and 2049)
.... data S0..1base64BinaryThe actual signature content (XML DigSig. JWS, picture, etc.)

doco Documentation for this format