Patsiendi elulõpu tahteavaldus
0.1.0 - trial-use
Patsiendi elulõpu tahteavaldus, published by TEHIK. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/TEHIK-EE/ig-ee-pet/ and changes regularly. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
Example resources that are referenced in this IG, but are from external systems.
| Patsient Pauliine Jänes |
MPI patsiendi näidis |
These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.
| PET cancellation ($cancel) |
UC-AHD-056: cancels a confirmed patient's end-of-life directive (PET). A new version with status entered-in-error is created. The operation accepts no input parameters and answers HTTP 200 with an empty body. |
| PET confirmation ($complete) |
UC-AHD-055: confirms a patient's end-of-life directive (PET). Input is exactly one of: a digitally signed PET as a Binary (signedBinary) or a QuestionnaireResponse and Provenance collection Bundle for paper signing (bundle). Under the stage-1 mock configuration, the digital path parses the ASiC-E container without DigiDoc signature verification and stores it locally instead of DRIT. Where digital signing is not enabled, the digital path responds with HTTP 501. |
| Trusted person confirmation by a healthcare worker ($confirm) |
UC-AHD-058: a healthcare worker adds and confirms a trusted person who signed on paper during the appointment. Input is a collection Bundle with the RelatedPerson and the paper-signing Provenance. |
| Trusted person invitation acceptance ($complete) |
UC-AHD-060: the invitation recipient accepts the trusted person invitation with a digitally signed RelatedPerson (ASiC-E container). Under the stage-1 mock configuration, the operation parses the container without DigiDoc signature verification and stores it locally instead of DRIT. Where digital signing is not enabled, the operation responds with HTTP 501. |
| Trusted person invitation rejection ($reject) |
UC-AHD-060 alternative flow 2.2.1: the invitation recipient rejects the trusted person invitation. The operation accepts no input parameters. |
These define the properties by which a RESTful server can be searched. They can also be used for sorting and including related resources.
| AhdCounselingLast |
Custom parameter (UC-AHD-054): last=true returns only the chronologically latest valid counselling decision for the patient and linked persons. |
| AhdQuestionnaireResponseId |
Search for trusted-person invitations (Task) and trusted persons (RelatedPerson) by PET (QuestionnaireResponse) id. The relation runs through the trusted person and is resolved by the PET search service, so expression is deliberately unset. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| AHD consultation result (Observation) |
AHD consultation data stating whether the patient is allowed to sign their decision. If the consultant decides the patient should not be able to sign their document, the consultant must provide a reason. |
| AHD content (QuestionnaireResponse) |
The actual content of the AHD and the patient's wishes |
| AHD data bundle (Bundle) |
Bundle of data consisting of questionnaire response and the signature |
| AHD response signature (Binary) |
Binary resource of the AHD questionnaire response in asice container |
| AHD signature data (Provenance) |
Data about the signing process of the AHD questionnaire response. Provides info about when the signing occurred, whether the signer was the patient or a capable witness and the signature itself. |
| AHD trustee (RelatedPerson) |
Patient can request a trustee who will represent thir wishes when the patient is incapable of doing so. Difference with witness: witness represents the patient in the AHD signing process when the trustee represents the patient's wishes when the AHD has activated. |
| AHD trustee request (Task) |
The patient can request a person to be their representative in the AHD employing process. The request can be made by the patient or a healthcare practitioner and the performer will be the requested trustee. |
| AHD trustee's data bundle (Bundle) |
Bundle of data consisting of information who the trustee is and their signature agreeing to be the patient's representative. |
| AHD trustee's signature (Binary) |
Binary resource of the AHD RelatedPerson in asice container |
| AHD trustee's signature data (Provenance) |
Data about the signing process when a person agrees to be a patient's trustee represeting their wishes. |
| AHD witness (RelatedPerson) |
If the patient is physically incapable of filling out their AHD document and signing it (while being capable of decision-making), a witness must be provided who will fill out the content in paper form sign the document on their behalf. Difference with trustee: witness represents the patient in the AHD signing process when the trustee represents the patient's wishes when the AHD has activated. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| AHD content reference |
Reference to the content that the trustee is connected with. |
||||
| AHD trustee status (Code) |
|
||||
| AHD witness reference |
Reference to the witness if a witness was used in the AHD signing process |
||||
| Digitally signed (Boolean) |
Shows whether the AHD content was filled and signed digitally by the patient (via National Health Portal Terviseportaal) or as a paper format by the patient or a witness (digitalized by the practitioner via TJT). |
These define sets of codes used by systems conforming to this implementation guide.
| AHD QuestionnaireResponse lubatud staatused |
|
|||
| AHD lubatud keeled |
Lubatud keeled patsiendi elulõpu tahteavalduse jaoks: eesti, inglise, vene. |
|||
| PET allkirjastaja roll |
Allkirjastaja roll: patsient (datasubject) või tunnistaja (legal). |
|||
| PET nõustamise otsuse staatus |
|
|||
| Usaldusisiku kutse staatus |
Usaldusisiku kutse (Task) lubatud staatused: ootel, kinnitatud, tagasilükatud. Alamhulk FHIR task-status koodisüsteemist. |
|||
| Usaldusisiku staatus |
Usaldusisiku lubatud staatused, alamhulk FHIR task-status koodisüsteemist |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Nõustamise otsuse näidis - negatiivne |
Näidis PET nõustamise otsus, kus patsiendil ei ole lubatud PET allkirjastada |
| Nõustamise otsuse näidis - positiivne |
Näidis PET nõustamise otsus, kus patsiendil on lubatud PET allkirjastada |
| PET vorm täidetud (näidis) |
Näidis vastus patsiendi elulõpu tahteavaldusele (PET) |
| Perearsti näidis |
Näidis arst, kes võib läbi viia PET nõustamise |
| Tervishoiuasutuse näidis |
Näidis organisatsioon, kus PET nõustamine toimus |
| Tunnistaja näidis |
Näidis tunnistaja AHD kontekstis |
| Usaldusisiku näidis |
Näidis usaldusisik AHD kontekstis |