Page Status: updated 2022-06-02 (Work in progress)

Consent scenarios

Introduction

There are two different Provenance profiles for documenting valid data combinations for a Provenance related to a Consent.

Details

The differences between each specialtized profile and the general Provenance profile, NLLProvenance, are highlighted in black in the rendered structures below, i.e. common rules are grayed out.

Multi dose dispensing consent

The profile NLLProvenanceConsentMultiDose documents the valid data combinations in a Provencance related to a multi dose dispensing consent.

For this type of consent the following special contraints apply:

  • the 'target' must point to a multi dose dispensing consent resource.
  • the 'reason' attribute is not used.
  • the 'activity' must be from the value set multidosedispconsent-activity-types
  • the 'agent.who' must point to a practitioner resource.

targetS Σ I1..*Reference(NLLMultiDoseDispConsent)
occurredDateTimedateTime
recordedS Σ1..1instant
policy0..*uri
locationI0..1Reference(Location)
systemS Σ0..1uri
versionS Σ0..1string
codeS Σ1..1code
displayΣ0..1string
userSelectedΣ0..1boolean
textΣ0..1string
typeS Σ1..1CodeableConceptBinding
role0..*CodeableConcept
whoS Σ I1..1Reference(NLLPractitioner)
onBehalfOfI0..1Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization)
roleΣ1..1codeBinding
whatΣ I1..1Reference(Resource)
agent0..*see (agent)
signature0..*Signature

Access consent

The profile NLLProvenanceConsentAccess documents the valid data combinations in a Provencance related to an access consent.

For this type of consent the following special contraints apply:

  • the 'target' must point to a access consent resource.
  • the 'reason' attribute is not used.
  • the 'activity' must be from the value set accessconsent-activity-types
  • the 'agent.who' must point to a practitioner resource.
    targetS Σ I1..*Reference(NLLAccessConsent)
    occurredDateTimedateTime
    recordedS Σ1..1instant
    policy0..*uri
    locationI0..1Reference(Location)
    systemS Σ0..1uri
    versionS Σ0..1string
    codeS Σ1..1code
    displayΣ0..1string
    userSelectedΣ0..1boolean
    textΣ0..1string
    typeS Σ1..1CodeableConceptBinding
    role0..*CodeableConcept
    whoS Σ I1..1Reference(NLLPractitioner)
    onBehalfOfI0..1Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization)
    roleΣ1..1codeBinding
    whatΣ I1..1Reference(Resource)
    agent0..*see (agent)
    signature0..*Signature