Consent

Consent Resource

This HL7 FHIR-compliant resource endpoint providing details and position information for consent where services are provided and resources and participants may be stored, found, contained, or accommodated.

PharmaNet

For PharmaNet, a patient can protect their medication profile using a protective keyword. Only specific system profiles (types) are able to manage that protective keyword for the patient. This is logically a mechanism supporting consent to access, which I why the keyword maintenance capability is part of the Consent resource.

Supported HL7-v2 Interactions

"contentType": "x-application/hl7-v2+er7"

PharmaNet Interaction	Version	Hl7-v2 Request	Required System Scope
Patient Keyword Maintenance TCP.00.50	PNet-R70.5	TCP-00_REQUEST	system/Consent.write, or user/Consent.write

Permissions

The resource endpoint examines the HL7-v2 transaction type submitted and then applies a permissions check, examining the access token provided to ensure that the calling client applications has obtained the correct permissions to allow the request to be processed. If not an HTTP 40x Error Code will be returned, without any HL7-v2 response payload. The permission scopes are based on SMART on FHIR specifications.

Example TCP.00.50 Request

TBD

The REST HL7 FHIR DocumentReference request using HTTP POST

TBD