- FHIR Encounter 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 Encounter dataset is an interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. A patient encounter is further characterized by the setting in which it takes place. Amongst them are ambulatory, emergency, home health, inpatient and virtual encounters.
Get The Data
- ResearchNon-Commercial, Share-Alike, Attribution Free Forever
- CommercialCommercial Use, Remix & Adapt, White Label Log in to download
An Encounter encompasses the lifecycle from pre-admission, the actual encounter (for ambulatory encounters), and admission, stay and discharge (for inpatient encounters). During the encounter, the patient may move from practitioner to practitioner and location to location.
Because of the broad scope of Encounter, not all elements will be relevant in all settings. For this reason, admission/discharge related information is kept in a separate Hospitalization component within Encounter. The class element is used to distinguish between these settings, which will guide further validation and application of business rules.
There is also substantial variance from organization to organization (and between jurisdictions and countries) on which business events translate to the start of a new Encounter, or what level of aggregation is used for Encounter. For example, every single visit of a practitioner during hospitalization may lead to a new instance of Encounter, but depending on local practice and the systems involved, it may well be that this is aggregated to a single instance for a whole hospitalization. Even more aggregation may occur where jurisdictions introduce groups of Encounters for financial or other reasons. Encounters can be aggregated or grouped under other Encounters using the part of the element.
Encounter instances may exist before the actual encounter takes place to convey pre-admission information, including using Encounters elements to reflect the planned start date or planned encounter locations. In this case the status element is set to ‘planned’.
The Hospitalization component is intended to store the extended information relating to a hospitalization event. It is always expected to be the same period as the encounter itself. Where the period is different, another encounter instance should be used to capture this information as a part of this encounter instance.
The Procedure and encounter have references to each other, and these should be to different procedures; one for the procedure that was performed during the encounter (stored in Procedure.encounter), and another for cases where an encounter is a result of another procedure (stored in Encounter.indication) such as a follow-up encounter to resolve complications from an earlier procedure.
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 Encounter 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|
|Encounter||resourceType||This is a Encounter resource||Encounter|
|Encounter||id||#/definitions/id||The logical id of the resource|
|Encounter||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.|
|Encounter||implicitRules||#/definitions/uri||A reference to a set of rules that were followed when the resource was constructed|
|Encounter||_implicitRules||#/definitions/Element||Extensions for implicitRules|
|Encounter||language||#/definitions/code||The base language in which the resource is written.|
|Encounter||_language||#/definitions/Element||Extensions for language|
|Encounter||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|
|Encounter||contained||array||These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently|
|Encounter||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|