Mobile Cross-Enterprise Document Data Element Extraction (mXDE)
1.3.0 - Trial-Implementation International flag

This page is part of the Mobile Cross-Enterprise Document Data Element Extraction (mXDE) (v1.3.0: Publication) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Resource Profile: mXDE Provenance

Official URL: https://profiles.ihe.net/ITI/mXDE/StructureDefinition/IHE.ITI.mXDE.Provenance Version: 1.3.0
Active as of 2023-08-04 Computable Name: IHE_mXDE_Provenance

Provenance profile for use in mXDE when the data-elements (Resources pointed to by target) come from an XDS or MHD document. There will be one Provenance record for each document that has been decomposed by mXDE.

  • policy will be urn:ihe:iti:mxde:2023:document-provenance-policy to indicate mXDE produced provenance
  • target will point at ALL of the data found within the document
    • some target resources will be only found in the document
    • some target resources may have been found in other documents
  • activity will be Derivation to indicate the target resources were derived from documents
  • recorded will indicate when the document was decomposed into these target resources
  • agent will identify the software/service that implements the decomposition of the documents
    • this agent would be type assembler as it has assembled the FHIR Resources
    • this agent should describe the version of the software so as to understand data translation rules used
    • this agent may be a Resource or may be Contained depending on environment policy
  • other agent elements may be included
  • entity will point at the DocumentReference for the document from which the target data came

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Provenance

NameFlagsCard.TypeDescription & Constraintsdoco
.. Provenance 0..*ProvenanceWho, What, When for a set of resources
... modifierExtension 0..0
... target 1..*Reference(Resource)The FHIR Resource elements found in the Document
... policy 1..1uriPolicy or plan the activity was defined by
Required Pattern: urn:ihe:iti:mxde:2023:document-provenance-policy
... activity 1..1CodeableConceptActivity that occurred
Required Pattern: At least the following
.... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
..... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/w3c-provenance-activity-type
..... code1..1codeSymbol in syntax defined by the system
Fixed Value: Derivation
... Slices for agent 1..*BackboneElementActor involved
Slice: Unordered, Open by pattern:type
.... agent:theAssembler 1..1BackboneElementThe Assembler of the FHIR Resources
..... type 1..1CodeableConceptHow the agent participated
Required Pattern: At least the following
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/provenance-participant-type
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: assembler
..... who 1..1Reference(Device) {c, r}Who participated
... entity 1..1BackboneElementThe DocumentReference from which these resources came
.... role 1..1codederivation | revision | quotation | source | removal
Required Pattern: source
.... what 1..1Reference(DocumentReference)Identity of entity
.... agent 0..0

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron