Fhir Consent Resources Mapping To Kantara Consent Receipt

I actually similar the piece of employment that Kantara is doing amongst Consent Receipt . I recollect they are doing what is needed. Speci...

I actually similar the piece of employment that Kantara is doing amongst Consent Receipt. I recollect they are doing what is needed. Specifically they are non trying to define an internal consent resource, nor ane that would become from ane information controller to to a greater extent than or less other information controller.

They are focused on giving the Individual something (a receipt) that is bear witness of the Consent Ceremony, in addition to contains the price agreed to. In this way, the Individual has bear witness that tin give notice endure used afterward when their consent price induce got been violated. Much similar a retail receipt is used yesteryear a consumer when the affair they bought turns out to endure broken or defective.

The diagram hither is the Kantara Consent Receipt

Perspective deviation betwixt FHIR in addition to Kantara:

The FHIR Consent is shown here

The Kantara Consent Receipt is intended to endure a self-contained message, where the FHIR Consent is ane Resource to endure used inside a FHIR infrastructure. The FHIR Consent is only focused on the consent specifics.

Thus to exercise a consummate equivalent ane would take away to gather from FHIR:

Bundle { MessageHeader(1..1), Consent (1..1), Provenance(1..1)}

Where:

Bundle assemblies everything together
MessageHeader explains to whom the message is going, in addition to from who it originates

I am assuming a pushed message, but FHIR clearly tin give notice endure used RESTfully, or a Document could endure created.

Provenance carries the proof of origination (signatures)
Consent specifics

Mapping FHIR Consent to Kantara Consent Receipt.

FHIR Consent

Kantara Consent Receipt

identifier

4.3.5 Consent Receipt ID

status

(N/A - would endure active)

scope

(N/A - would endure fixed at privacy-consent)

Not good mapped:

I am pleased in addition to rattling surprised at how good these map. The next items are where at that spot was differences. These differences appear reasonable given the run of each, in addition to capabilities of the environments.

The next items from the Kantara Consent Receipt exercise map, but non perfectly.

4.3.4 Collection Method - a description of the method yesteryear which consent was obtained

for FHIR, the electrical flow presumption is that the information is collected during treating the patient for healthcare reasons. This electrical flow presumption is probable non going to endure truthful equally FHIR matues

4.5.8 Primary Purpose -- indicates if a run is role of a marrow service of the PII controller

Seems to endure a agency to differentiate main run from secondary.
FHIR Consent addresses run of exercise regardless of main or secondary

4.5.9 Termination - weather condition for the outcome of consent. link to policy defining how consent or run is terminated.

FHIR Consent has timeframe to automatically terminate, but does non address how the patient would accept action

There are a few additional capabilities of the FHIR Consent that are non soundless represented inwards Kantara

verification -- these elements are at that spot to handgrip who verified the consent ceremony. I am non convinced that this is unremarkably needed.
dataPeriod -- oftentimes a patient is willing to permit to a greater extent than or less information to flow, but mightiness desire to block information from a specifically sensitive catamenia of time. The timeframe is an slowly affair to identify, in addition to to enforce.
data -- FHIR nosotros tin give notice dot at just which information is controlled yesteryear this rule
nested provisions -- FHIR Consent tin give notice defined nested provisions. Thus enable this, but non that...

Consent is a deep topic that I induce got many articles