- FHIR Consent Resource
- Electronic Health Records Exchange Through FHIR
- Medical Terminology
- Processes Data
- Processes Information
- Processes Documentation
- Health Information Exchange
- Electronic Health Records
- FHIR Smart
- Smart on FHIR
The Consent Resource is a record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.
Get The Data
- ResearchNon-Commercial, Share-Alike, Attribution Free Forever
- CommercialCommercial Use, Remix & Adapt, White Label Log in to download
The purpose of this Resource is to be used to express Consent regarding Healthcare. There are four anticipated uses for the Consent Resource, all of which are written or verbal agreements by a healthcare consumer or a personal representative, made to an authorized entity concerning authorized or restricted actions with any limitations on purpose of use, and handling instructions to which the authorized entity must comply:
– Privacy Consent Directive: Agreement to collect, access, use or disclose (share) information.
– Medical Treatment Consent Directive: Consent to undergo a specific treatment (or record of refusal to consent).
– Research Consent Directive: Consent to participate in research protocol and information sharing required.
– Advance Care Directives: Consent to instructions for potentially needed medical treatment (e.g. DNR).
– This resource is scoped to cover all four uses, but at this time, only the privacy use case is modeled. The scope of the resource may change when the other possible scopes are investigated, tested, or profiled.
An FHIR Consent Directive instance is considered the encoded legally binding Consent Directive if it meets requirements of a policy domain requirements for an enforceable contract. In some domains, electronic signatures of one or both of the parties to the content of an encoded representation of a Consent Form is deemed to constitute a legally binding Consent Directive. Some domains accept a notary’s electronic signature over the wet or electronic signature of a party to the Consent Directive as the additional identity proofing required to make an encoded Consent Directive legally binding. Other domains may only accept a wet signature or might not require the parties’ signatures at all.
Whatever the criteria are for making an encoded FHIR Consent Directive legally binding, anything less than a legally binding representation of a Consent Directive must be identified as such, i.e., as a derivative of the legally binding Consent Directive, which has a specific usage in Consent Directive workflow management.
Fast Healthcare Interoperability Resources (FHIR) is a draft standard describing data formats and elements (known as “resources”) and an application programming interface (API) for exchanging electronic health records. The standard was created by the Health Level Seven International (HL7) health-care standards organization.
Its goal is to facilitate interoperation between legacy healthcare systems, to make it easy to provide healthcare information to healthcare providers and individuals on a wide variety of devices from computers to tablets to cell phones, and to allow third-party application developers to provide medical applications which can be easily integrated into existing systems.
FHIR provides an alternative to document-centric approaches by directly exposing discrete data elements as services. For example, basic elements of healthcare like patients, admissions, diagnostic reports and medications can each be retrieved and manipulated via their own resource URLs (Uniform Resource Locators). FHIR was supported at an American Medical Informatics Association meeting by many EHR (Electronic Health Record) vendors which value its open and extensible nature.
About this Dataset
John Snow Labs; Health Level Seven International;
|Source License URL|
|Source License Requirements||
FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR
FHIR Consent Resource, Electronic Health Records Exchange Through FHIR
|Concept_Name||Name of the concept in the FHIR structure||string||required : 1|
|Computer_Ready_Name||A Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this.||string||-|
|Type||The type the structure describes.||string||-|
|Description||A free text natural language description of the structure and its use||string||-|
|Items||The value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value.||string||-|
|Enum||The enum is used to restrict a value to a fixed set of values. It must be an array with at least one element, where each element is unique.||string||-|
|Required||The value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value.||string||-|
|Const||The value of this keyword can be anything. The data is valid if it is deeply equal to the value of the keyword.||string||-|
|Concept Name||Computer Ready Name||Type||Dollar Ref||Description||Items||Enum||Required||Const|
|Consent||resourceType||This is a Consent resource||Consent|
|Consent||id||#/definitions/id||The logical id of the resource|
|Consent||meta||#/definitions/Meta||The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.|
|Consent||implicitRules||#/definitions/uri||A reference to a set of rules that were followed when the resource was constructed|
|Consent||_implicitRules||#/definitions/Element||Extensions for implicitRules|
|Consent||language||#/definitions/code||The base language in which the resource is written.|
|Consent||_language||#/definitions/Element||Extensions for language|
|Consent||text||#/definitions/Narrative||A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data|
|Consent||contained||array||These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently|
|Consent||extension||array||May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable|