extension shown: fhir [x]

Encounter

Defined in the fhir.schema.org extension.
Canonical URL: http://schema.org/Encounter

Thing > Resource > DomainResource > Encounter
workflow.encounter > Encounter

Base StructureDefinition for Encounter Resource

Usage: Fewer than 10 domains
PropertyExpected TypeDescription
Properties from Encounter
Encounter.appointment Appointment The appointment that scheduled this encounter.
Encounter.class encounter-class inpatient | outpatient | ambulatory | emergency +.
Encounter.episodeOfCare EpisodeOfCare Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care, and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years).
Encounter.hospitalization BackboneElement Details about the admission to a healthcare service.
Encounter.hospitalization.admitSource encounter-admit-source From where patient was admitted (physician referral, transfer).
Encounter.hospitalization.admittingDiagnosis Condition The admitting diagnosis field is used to record the diagnosis codes as reported by admitting practitioner. This could be different or in addition to the conditions reported as reason-condition(s) for the encounter.
Encounter.hospitalization.destination Location Location to which the patient is discharged.
Encounter.hospitalization.dietPreference encounter-diet Diet preferences reported by the patient.
Encounter.hospitalization.dischargeDiagnosis Condition The final diagnosis given a patient before release from the hospital after all testing, surgery, and workup are complete.
Encounter.hospitalization.dischargeDisposition encounter-discharge-disposition Category or kind of location after discharge.
Encounter.hospitalization.origin Location The location from which the patient came before admission.
Encounter.hospitalization.preAdmissionIdentifier Identifier Pre-admission identifier.
Encounter.hospitalization.reAdmission Text Whether this hospitalization is a readmission and why if known.
Encounter.hospitalization.specialArrangement encounter-special-arrangements Wheelchair, translator, stretcher, etc.
Encounter.hospitalization.specialCourtesy encounter-special-courtesy Special courtesies (VIP, board member).
Encounter.identifier Identifier Identifier(s) by which this encounter is known.
Encounter.incomingReferral ReferralRequest The referral request this encounter satisfies (incoming referral).
Encounter.indication Procedure  or
Condition 
Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure.
Encounter.length Quantity Quantity of time the encounter lasted. This excludes the time during leaves of absence.
Encounter.location BackboneElement List of locations where the patient has been during this encounter.
Encounter.location.location Location The location where the encounter takes place.
Encounter.location.period Period Time period during which the patient was present at the location.
Encounter.location.status encounter-location-status The status of the participants' presence at the specified location during the period specified. If the participant is is no longer at the location, then the period will have an end date/time.
Encounter.partOf Encounter Another Encounter of which this encounter is a part of (administratively or in time).
Encounter.participant BackboneElement The list of people responsible for providing the service.
Encounter.participant.individual Practitioner  or
RelatedPerson 
Persons involved in the encounter other than the patient.
Encounter.participant.period Period The period of time that the specified participant was present during the encounter. These can overlap or be sub-sets of the overall encounters period.
Encounter.participant.type encounter-participant-type Role of participant in encounter.
Encounter.patient Patient The patient present at the encounter.
Encounter.period Period The start and end time of the encounter.
Encounter.priority encounter-priority Indicates the urgency of the encounter.
Encounter.reason encounter-reason Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.
Encounter.serviceProvider Organization An organization that is in charge of maintaining the information of this Encounter (e.g. who maintains the report or the master service catalog item, etc.). This MAY be the same as the organization on the Patient record, however it could be different. This MAY not be not the Service Delivery Location's Organization.
Encounter.status encounter-state planned | arrived | in-progress | onleave | finished | cancelled.
Encounter.statusHistory BackboneElement The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them.
Encounter.statusHistory.period Period The time that the episode was in the specified status.
Encounter.statusHistory.status encounter-state planned | arrived | in-progress | onleave | finished | cancelled.
Encounter.type encounter-type Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation).
Properties from DomainResource
DomainResource.contained Resource These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
DomainResource.extension Extension May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
DomainResource.modifierExtension Extension May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
DomainResource.text Narrative A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Properties from Resource
Resource.id Text The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Resource.implicitRules Text A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.
Resource.language http://tools.ietf.org/html/bcp47 The base language in which the resource is written.
Resource.meta Meta The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.
Properties from Thing
additionalType URL An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. In RDFa syntax, it is better to use the native RDFa syntax - the 'typeof' attribute - for multiple types. Schema.org tools may have only weaker understanding of extra types, in particular those defined externally.
alternateName Text An alias for the item.
description Text A description of the item.
disambiguatingDescription Text A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation.
image URL  or
ImageObject 
An image of the item. This can be a URL or a fully described ImageObject.
mainEntityOfPage URL  or
CreativeWork 
Indicates a page (or other CreativeWork) for which this thing is the main entity being described.

See background notes for details.
Inverse property: mainEntity.
name Text The name of the item.
potentialAction Action Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.
sameAs URL URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Freebase page, or official website.
url URL URL of the item.


Instances of Encounter may appear as values for the following properties
PropertyOn TypesDescription
CarePlan.context CarePlan Identifies the context in which this particular CarePlan is defined.
Communication.encounter Communication The encounter within which the communication was sent.
CommunicationRequest.encounter CommunicationRequest The encounter within which the communication request was created.
Composition.encounter Composition  or
measurereport 
Describes the clinical encounter or type of care this documentation is associated with.
Condition.encounter Condition Encounter during which the condition was first asserted.
DeviceUseRequest.encounter DeviceUseRequest An encounter that provides additional context in which this request is made.
DiagnosticOrder.encounter DiagnosticOrder An encounter that provides additional information about the healthcare context in which this request is made.
DiagnosticReport.encounter DiagnosticReport The link to the health care event (encounter) when the order was made.
DocumentReference.context.encounter DocumentReference Describes the clinical encounter or type of care that the document content is associated with.
Encounter.partOf Encounter Another Encounter of which this encounter is a part of (administratively or in time).
Flag.encounter Flag This alert is only relevant during the encounter.
Immunization.encounter Immunization The visit or admission or other contact between patient and health care provider the immunization was performed as part of.
List.encounter List The encounter that is the context in which this list was created.
MedicationAdministration.encounter MedicationAdministration The visit, admission or other contact between patient and health care provider the medication administration was performed as part of.
MedicationOrder.encounter MedicationOrder A link to a resource that identifies the particular occurrence of contact between patient and health care provider.
NutritionOrder.encounter NutritionOrder An encounter that provides additional information about the healthcare context in which this request is made.
Observation.encounter Observation  or
devicemetricobservation 
The healthcare event (e.g. a patient and healthcare provider interaction) during which this observation is made.
Procedure.encounter Procedure The encounter during which the procedure was performed.
ProcedureRequest.encounter ProcedureRequest The encounter within which the procedure proposal or request was created.
QuestionnaireResponse.encounter QuestionnaireResponse Encounter during which this set of questionnaire response were collected. When there were multiple encounters, this is the one considered most relevant to the context of the answers.
ReferralRequest.encounter ReferralRequest The encounter at which the request for referral or transfer of care is initiated.
RiskAssessment.encounter RiskAssessment The encounter where the assessment was performed.
VisionPrescription.encounter VisionPrescription A link to a resource that identifies the particular occurrence of contact between patient and health care provider.

Available supertypes defined in extensions

Schema Version 2.2