FHIR Consent Resource mapping to Kantara Consent Receipt

I love the work Cantara does with permission. I think they do what’s needed. In particular, they are not trying to identify an internal source of approval, and no one moves from a data controller to another data controller. It focuses on giving the individual something (a receipt) forming proof of licensing regulations and containing agreed conditions. In this way, the individual has evidence that can be used later if the terms of his or her authorization are violated. The consumer uses the same thing as sales confirmation if it appears that the purchased product is defective or defective.

The table here is the acceptance of Qantara’s approval

Theoretical difference between FHIR and Kantara:
FHIR shows approval here

Qantara’s approval is a self-contained message. FHIR approval is one of the resources used in the FHIR infrastructure. FHIR’s permission only applies to the approval details.

Therefore, creating a complete equivalent device should be added from FHIR:

Package {MessageHeader (1..1), Approval (1..1), Provence (1..1)}


The gathering collects everything.
MessageHeader explains who should be the message and who will create it
I thought a message was paid, but the FHIR could certainly be used uniquely or a document could be created.
Proof of origin (signatures).
certification details
Appointment of FHIR approval of Qantara reception.

Statement of authorization FHIR Qantara
ID 4.3.5 is a receipt acknowledgment
State (N / A – active)
Domain (unavailable – agrees with privacy permissions)
Category approval type 4.5.5
Patient 4.4.1 Recognized Personal Identity
dateTime 4.3.3 Approval of the timestamp
Performance 4.4.3 PII controller
4.4.5 PII control contact
4.4.6 PII communication controller
4.4.6 Address of PII controller
4.4.7 PII-Controller E-Mail
4.4.8 PII phone controller
4.4.9 PII Monitor URL
4.4.4 Processing
4.4.3 pii driver (including all contact information)
Origin [x] 4.7 Presentation and Presentation.
The rules
Authority 4.3.2 Jurisdiction
Policy 4.4.10 Privacy Policy
proven with
Review date
Provisions 4.5.1 Services
End Time 4.5.9 Termination
Role 4.5.10 Disclosure of third parties
Reference 4.5.11 Third party name
Activity 4.5.2 Services
securityLabel 4.5.12 Sensitive PII
4.5.13 sensitive PII class
Goal 4.5
4.5.4 Purpose
4.5.5 Purpose
4.5.8 Main purpose
Class 4.5.7 PII categories
Codes 4.5.7 PII Categories
data duration
The data

Badly defined:
I was happy and I was surprised how good this card was. Various following elements. Differences are appropriate given the particular purpose and capabilities of the environment.

The following acceptance elements of Bow Acceptance are not assigned, but not.
4.3.4 Survey method: illustrates the manner in which the permit is obtained
FHIR currently estimates data will be collected during the patient’s medical treatment. Probably this current assumption is correct as long as the stability of the FHIR
4.5.8 Main purpose: Indicates whether the goal is part of the central service for a PII controller
It looks like a way to distinguish between primary and secondary goals.
FHIR determines the approval of specified use regardless of primary or secondary
4.5.9 Termination – Permit Termination Conditions. Link a policy indicating how endorsement or purpose should end.
FHIR’s permission has a timeline for automatic termination, but it does not respond to how the patient is acting
There are several more ways to approve the FHIR that has not yet been represented in Kantara
Validation: These elements exist for reviewers on approval regulations. I am not convinced that it is indispensable.
Data Age: The patient is usually willing to allow some data to flow but wants to block the data for a sensitive period of time. The season is easy to recognize and apply.
Data – FHIR We can specify the data that is controlled by this policy
Temporary provisions: The FHIR Agreement may provide the overlapping provisions. So allow it, but not so …
Approval is a deep subject. I have many articles.

Leave a Reply

Your email address will not be published. Required fields are marked *