CIMI_Clinical.Provenance

Class Attribution

Documentation:

Attribution provides a formal pattern and reusable structure for attributes of a record that describes an activity in a process involved in producing, delivering or otherwise influencing that resource. Attribution provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which may impact security, privacy, and trust policies. Attribution provides a common reference model pattern that may be included directly within a clinical statement (e.g., the metadata associated with the recording of a clinical statement in a system) or within the Provenance pattern when it is preferrable to have such information external to but referencing the clinical statement (see Provenance). Note that, when included directly within a clinical statement, updates made to attribution attribute values will result in a versioning change in the instance. When part of the Provenance class, updates to provenance do not result in an update of the clinical statement referenced by the Provenance class (see Provenance.target).

Ancestors:

• Locatable
• • Attribution

Descendants:

Property Summary

Properties

Property Name	Type and Description	Existence	Cardinality
identifier	List<Identifier> A token that uniquely identifies the act of attribution.	0..1	0..*
activity	Concept An activity is something that occurs over a period of time and acts upon or with entities; it may include asserting, recording, verifying, consuming, processing, transforming, modifying, relocating, using, or generating entities. The activity attribute should be used when attribution appears in a collection to distinguish the type of attributions based on the activity described. When Attribution is the type of a model attribute such as 'recorded', the activity attribute should be left out as specifying the activity would be redundant.	0..1	N/A
recordedOn	TemporalValue The time at which the activity was recorded.	0..1	N/A
recordedBy	Party The person or entity capturing the attribution information.	0..1	N/A
activityTimeRange	IntervalValue<Date> The period during which the activity occurred.	0..1	N/A
reason	List<Concept> The reason that the activity was taking place.	0..1	0..*
location	List<Location> Where the activity occurred, if relevant.	0..1	0..*
policy	List<UriType> Policy or plan that defines the activity. Typically, a single activity may have multiple applicable policy documents, such as patient consent, guarantor funding, etc.	0..1	0..*
participant	List<PartyAssociation<P>> A person or other party responsible for execution of some facet of the activity. The agent in an activity for which it can be assigned some degree of responsibility for the activity taking place. The agent comprises both the party involved and its role.	0..1	0..*
entity	List<PartyAssociation<P>> An entity used in this activity.	0..1	0..*
signature	List<Signature> A digital signature on the target Reference(s). The signer should match a Attribution.participant. The purpose of the signature is indicated.	0..1	0..*
method	List<Concept> This component captures the method used to perform the activity. For instance, in Verified, it captures how verification is achieved (verbal, written, telephone, etc.). In a specimen collection, examples include sputum, finger stick.	0..1	0..*

Properties inherited from class Locatable

archetype_node_id, name, archetype_details