FHIR Encounter
E732180
FHIR Encounter is a FHIR resource that represents an interaction between a patient and healthcare provider(s) for the purpose of providing healthcare services or assessing the patient’s health status.
All labels observed (1)
| Label | Occurrences |
|---|---|
| FHIR Encounter canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8418871 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FHIR Encounter Context triple: [IHE MHD, usesResourceType, FHIR Encounter]
-
A.
Health Connect
Health Connect is a unified health and fitness data platform on Android that lets apps securely share and manage users’ wellness information in one place.
-
B.
FHIR STU3
FHIR STU3 is the third major release of the HL7 Fast Healthcare Interoperability Resources standard, defining structured formats and APIs for exchanging electronic healthcare data.
-
C.
ClinicalKey
ClinicalKey is a comprehensive clinical search engine and decision-support platform for healthcare professionals, providing access to medical textbooks, journals, guidelines, and multimedia content.
-
D.
FHIR R5 (preview)
FHIR R5 (preview) is the upcoming fifth major release of the HL7 Fast Healthcare Interoperability Resources standard, offering enhanced data models and interoperability features for exchanging healthcare information.
-
E.
Cloud Healthcare API
Cloud Healthcare API is a Google Cloud service that enables secure storage, management, and exchange of healthcare data using standard formats like HL7, FHIR, and DICOM.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: FHIR Encounter Target entity description: FHIR Encounter is a FHIR resource that represents an interaction between a patient and healthcare provider(s) for the purpose of providing healthcare services or assessing the patient’s health status.
-
A.
Health Connect
Health Connect is a unified health and fitness data platform on Android that lets apps securely share and manage users’ wellness information in one place.
-
B.
FHIR STU3
FHIR STU3 is the third major release of the HL7 Fast Healthcare Interoperability Resources standard, defining structured formats and APIs for exchanging electronic healthcare data.
-
C.
ClinicalKey
ClinicalKey is a comprehensive clinical search engine and decision-support platform for healthcare professionals, providing access to medical textbooks, journals, guidelines, and multimedia content.
-
D.
FHIR R5 (preview)
FHIR R5 (preview) is the upcoming fifth major release of the HL7 Fast Healthcare Interoperability Resources standard, offering enhanced data models and interoperability features for exchanging healthcare information.
-
E.
Cloud Healthcare API
Cloud Healthcare API is a Google Cloud service that enables secure storage, management, and exchange of healthcare data using standard formats like HL7, FHIR, and DICOM.
- F. None of above. chosen
Statements (75)
| Predicate | Object |
|---|---|
| instanceOf |
FHIR resource
ⓘ
clinical resource ⓘ |
| belongsToFHIRVersion |
FHIR R4
NERFINISHED
ⓘ
FHIR R5 NERFINISHED ⓘ |
| canReference |
Account
ⓘ
Appointment ⓘ Condition ⓘ EpisodeOfCare ⓘ Group ⓘ Location ⓘ Observation NERFINISHED ⓘ Organization NERFINISHED ⓘ Patient ⓘ Practitioner ⓘ PractitionerRole ⓘ Procedure ⓘ RelatedPerson ⓘ ServiceRequest ⓘ |
| definedIn | HL7 FHIR specification NERFINISHED ⓘ |
| hasCanonicalUrl | http://hl7.org/fhir/StructureDefinition/Encounter ⓘ |
| hasKeyElement |
account
ⓘ
admission ⓘ appointment ⓘ basedOn ⓘ class ⓘ classHistory ⓘ diagnosis ⓘ dietPreference ⓘ episodeOfCare ⓘ hospitalization ⓘ identifier ⓘ length ⓘ location ⓘ meta ⓘ partOf ⓘ participant ⓘ period ⓘ priority ⓘ reasonCode ⓘ reasonReference ⓘ serviceProvider ⓘ serviceType ⓘ specialArrangement ⓘ specialCourtesy ⓘ status ⓘ statusHistory ⓘ subject ⓘ subjectStatus ⓘ type ⓘ virtualService ⓘ |
| hasParticipant | healthcare provider(s) involved in the encounter ⓘ |
| hasPrimaryPurpose | represent an interaction between a patient and healthcare provider(s) ⓘ |
| hasPurpose |
document assessment of a patient’s health status
ⓘ
document provision of healthcare services ⓘ |
| hasResourceTypeCode | Encounter ⓘ |
| hasStatusValue |
cancelled
ⓘ
completed ⓘ entered-in-error ⓘ in-progress ⓘ onhold ⓘ planned ⓘ unknown ⓘ |
| hasSubject | patient or group receiving care ⓘ |
| hasTemporalExtent | period element ⓘ |
| isIdentifiedBy | identifier element ⓘ |
| isPartOfStandard | HL7 FHIR core resources set NERFINISHED ⓘ |
| isUsedFor |
emergency encounters
ⓘ
inpatient encounters ⓘ outpatient encounters ⓘ virtual or telehealth encounters ⓘ |
| supportsWorkflow |
billing and claims
ⓘ
care coordination ⓘ clinical documentation ⓘ quality reporting ⓘ |
| usesClassSystem | http://terminology.hl7.org/CodeSystem/v3-ActCode ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: FHIR Encounter Description of subject: FHIR Encounter is a FHIR resource that represents an interaction between a patient and healthcare provider(s) for the purpose of providing healthcare services or assessing the patient’s health status.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.