Difference between revisions of "Consent in Queries"
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 1: | Line 1: | ||
| + | Use-case: consent based on | ||
| + | *Legitimate relationship (UK term), Certificate of Care Relationship (Finnish term). Consent is explicit/implicit related to e.g. the fact the GP has a relationship with a Patient | ||
| + | *Consent form: granting acces to data, created/signed by patient | ||
| + | In queries, in Finland may need to send more that just the ID of the consent document instance, or the ID of the Certificate of Care Relationship. Consent may be in central reporsitory, in which case it may be referenced. May require a medical-records (or new) interaction to convey the consent. Depends on level of trust, in NL the ID may be sufficient, because during audit you better have the full document. | ||
| − | + | In US no national provider IDs, no PKI infrastructure, HIPAA. | |
| − | |||
| − | |||
| − | Emergency override: in v3 terms, see DetectedIssue and DetectedIssueManagament classes in the ControlAct wrapper. | + | Emergency override: in v3 terms, see DetectedIssue and DetectedIssueManagament classes in the ControlAct wrapper. Supply a (textual) reason for doing so as well. |
Note on Consent.txt: In terms of the consent model, a more accurate model might be to say that the consent is an instance of a consent definition, where the text of the definition reflects the "form". Alternatively, it could represent the complete filled in form, which would presumably address the subject, performer, etc. | Note on Consent.txt: In terms of the consent model, a more accurate model might be to say that the consent is an instance of a consent definition, where the text of the definition reflects the "form". Alternatively, it could represent the complete filled in form, which would presumably address the subject, performer, etc. | ||
Revision as of 20:07, 13 September 2006
Use-case: consent based on
- Legitimate relationship (UK term), Certificate of Care Relationship (Finnish term). Consent is explicit/implicit related to e.g. the fact the GP has a relationship with a Patient
- Consent form: granting acces to data, created/signed by patient
In queries, in Finland may need to send more that just the ID of the consent document instance, or the ID of the Certificate of Care Relationship. Consent may be in central reporsitory, in which case it may be referenced. May require a medical-records (or new) interaction to convey the consent. Depends on level of trust, in NL the ID may be sufficient, because during audit you better have the full document.
In US no national provider IDs, no PKI infrastructure, HIPAA.
Emergency override: in v3 terms, see DetectedIssue and DetectedIssueManagament classes in the ControlAct wrapper. Supply a (textual) reason for doing so as well.
Note on Consent.txt: In terms of the consent model, a more accurate model might be to say that the consent is an instance of a consent definition, where the text of the definition reflects the "form". Alternatively, it could represent the complete filled in form, which would presumably address the subject, performer, etc.
