JohnMoehrke RelatedPerson Consent
0.1.0 - ci-build International flag

JohnMoehrke RelatedPerson Consent - Local Development build (v0.1.0). See the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide

Authorized RelatedPerson

A RelatedPerson that has been justified and authorized by the Patient.

  • The RelatedPerson.patient must be the same as the Consent.patient
  • The Consent.provision.agent.reference must be the same as the RelatedPerson.id
  • The Consent is authorizing (permit) the RelatedPerson, and is not expired.
Consent profile for a RelatedPerson relationship

This defines the constraints on a Consent to indicate that a Patient has agreed and authorizes a Related Person.

  • status - would indicate active
  • category - would indicate patient consent specifically a delegation of authority
  • patient - would indicate the Patient resource reference for the given patient
  • dateTime - would indicate when the privacy policy was presented
  • performer - would indicate the Patient resource if the patient was presented, a RelatedPerson for parent or guardian
  • organization - would indicate the Organization who presented the privacy policy, and which is going to enforce that privacy policy
  • source - would point at the specific signed consent by the patient
  • policy.uri - would indicate the privacy policy that was presented. Usually, the url to the version specific policy
  • provision.type - permit - given there is no way to deny, this would be fixed at permit.
  • provision.agent.reference - would indicate the RelatedPerson resource
  • provision.agent.role - would indicate this agent is delegated authority
  • provision.purpose - would indicate some set of authorized purposeOfUse

Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide

Extension that points at an authorizing Consent

Used within a Resource to indicate that the activity enabled by the Resource is authorized by the Consent indicated. For example: Used within a RelatedParty to indicate the Consent the Patient has given authorizing the RelatedParty relationship to exist.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide

Authorization purposes for delegation access valueset

ValueSet of the Authorized purposesOfUse types

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide

Consent type that is authorizing a RelatedPerson

CodeSystem for authorizing Consent types for a RelatedPerson

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like

Simple Consent example

Consent justifying RelatedPerson and authorizing access by that RelatedPerson
Practitioner example doctor

Practitioner example for the doctor.
DocumentReference Consent Paperwork example

DocumentReference example of the paperwork of the Consent
Father - Related Person

Related Father of the Patient authorized by a Consent
Example Organization holding the data

The Organization that holds the data, and enforcing any Consents
Patient example

Patient example for completeness sake.