Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

 

FHIR resource link

httpshttp://www.hl7.org/fhir/R4B/consent.html

Status
colourGreen
titleCURRENT USED BY PSI

http://hl7.org/fhir/R5/consent.html

https://build.fhir.org/consent.html SIGNIFICANT CHANGES

FHIR definition

A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.

PSI use case

Consumer’s acceptance to T&C or other documentation

Required properties

(see details below)

  • tags

  • status [fhir]

  • scope [fhir]

  • category [fhir]

  • patient

  • performer

  • dateTime

  • organization

  • language

  • source

  • policy || policyRule

  • provision/dataPeriod.period

Extensions

Sept 2022 - enforcement of required properties for PSI under consideration

Sample payload

Code Block
{
  "resourceType": "Consent",
  "status": "active", //active | inactive
  "scope": {
    "coding": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/consentscope",
        "code": "patient-privacy"
      }
    ]
  },
  "category": [
    {
      "coding": [
        {
          "system": "http://loinc.org",
          "code": "59284-0"
        }
      ]
    }
  ],
  "patient": {
    "reference": "Patient/f001",
  },
  "performer":{
    "reference": "Patient/f001",
  },
  "dateTime": "2016-05-11",
  "organization": {
      "reference": "Organization/f001"
    },
  "language": "en",
  "sourceReference":{
	  // TODO
  },
  // Either a Policy or PolicyRule	policy.exists() or policyRule.exists()
  "policyRule": {
    "coding": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "code": "OPTIN"
      }
    ]
  }, 
  "provision": {
    "period": {
      "start": "1964-01-01",
      "end": "2016-01-01" //when person opt-outs
    }
  }
}

Resource Dependencies

Patient
Organization
DocumentReference

...

Property

Set

Notes

tags

Status
colourGreen
titleREQUIRED
[psi]

countryISO & projectID

status

Status
colourGreen
titleREQUIRED
[fhir]

draft | proposed | active | rejected | inactive | entered-in-error
For PSI:

  • active/rejected: set on consumer’s choice

  • inactive: set when superseded (in conjunction with period end date)

period

Status
colourRed
titleFHIR v5

Status
colourGreen
titleREQUIRED
[psi]

Effective period for this Consent. Effective period for this Consent Resource and all provisions unless specified in that provision

scope

Status
colourGreen
titleREQUIRED
[fhir 4.3] - not in 5.0

For PSI’s use case, we will normally set scope to:
patient-privacy (Privacy Consent): Agreement to collect, access, use or disclose (share) information

category

Status
colourGreen
titleREQUIRED
[fhir]

“59284-0” based on http://loinc.org Patient Consent

patient

Status
colourGreen
titleREQUIRED
for patients [psi]

WILL CHANGE for 5.0

If the consent relates to a patient [psi] the related record must be passed.

performer

Status
colourGreen
titleREQUIRED
[psi]

patient id - if collected directly from the consumer - e.g. on a bot

practitioner id - if collected by a health worker

dateTime

Status
colourGreen
titleREQUIRED
[psi]

date time that the patient agreed to the consent -

DateTime should be recorded with associated TimeZone

09:30:10Z - UTC

09:30:10-06:00 -6h from UTC

09:30:10+06:00 +6h from UTC

DateTime should be UTC - Frontend apps and Analytics will need to convert to local timezone.

organization

Status
colourGreen
titleREQUIRED
[psi]

reference to Organization ID - who issued the consent document

language

Status
colourGreen
titleREQUIRED
[psi]

bpc-47 - en/es/fr/

source

Status
colourGreen
titleREQUIRED
[psi]

/source reference = document reference ID

DocumentReference - FHIR

policy OR policyRule

Status
colourGreen
titleREQUIRED
[fhir]

code: OPTIN (see code example)

provision/dataPeriod.period

Status
colourGreen
titleREQUIRED
[psi]

the time period for which the consent applies, normally just start date. The end date is set if the patients opt-out or the consent is superseded by another consent.

In

Status
colourRed
titleFHIR v5
, a field period is set on the top level of the Consent (see Jira ticket for that change). The consent.period is the effective period for this Consent Resource and all provisions unless specified in that provision

So data would be moved from consent.provision.period to consent.period.

*in addition to: countryISO & projectID