Page Status: updated 2022-03-24

Data lock scenarios

Introduction

The profile NLLProvenanceBasicDataLock documents provenances related to a Basic with code="datalock" for Data lock (sv Spärr).

Details

The differences between the NLLProvenanceBasicDataLock profile and the general NLLProvenance profile are highlighted in black in the rendered structure below, i.e. common rules are grayed out.

When creating or updating a patient's data lock there are a number or additional constraints to the Provenance profile:

  • the 'target' must point to a Basic resource with code="datalock".
  • the 'reason' attribute is not used
  • the 'activity' must be from the value set dl-activity-types
  • NB! 'agent.who' can point either to a Practitioner resource or a Patient resource

targetS Σ I1..*Reference(NLLDataLock)
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 | NLLPatient)
onBehalfOfI0..1Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization)
roleΣ1..1codeBinding
whatΣ I1..1Reference(Resource)
agent0..*see (agent)
signature0..*Signature