| Property Name | Type and Description | Existence | Cardinality |
|---|---|---|---|
accountId |
Identifier
The patient’s account number in the context of the admitting or providing institution.
|
0..1
| N/A
|
accountStatus |
Concept
"Contains the account status." - HL7 Version 2.8, PV1-41. Note that HL7 does not suggest any values for this code (in User-defined Table 117).
|
0..1
| N/A
|
alternateVisitId |
List<Identifier>
"Contains the alternative, temporary, or pending optional visit ID number to be used if needed. Multiple alternate identifiers may be sent." - HL7 Version 2.8, PV1-50
Uniquely identifies this patient visit using an identification scheme other than the one used for the "id" property. This allows for different systems or organizations to assign different identifiers to the same visit.
|
0..1
| 0..*
|
ambulatoryStatus |
Concept
"Indicates any permanent or transient handicapped conditions." - HL7 Version 2.8, PV1-15.
Possible values include (from HL7 V2 Table 9): No functional limitations; Ambulates with assistive device; Wheelchair/stretcher bound; Comatose - non-responsive; Disoriented; Vision impaired; Hearing impaired; Speech impaired; Non-English speaking; Functional level unknown; Oxygen therapy; Special equipment (tubes, IVs, catheters); Amputee; Mastectomy; Paraplegic; Pregnant.
|
0..1
| N/A
|
chargePriceIndicator |
Concept
"Contains the code used to determine which price schedule is to be used for room and bed charges." - HL7 Version 2.8, PV1-21. Note that HL7 does not suggest any values for this code (in User-defined Table 32).
|
0..1
| N/A
|
chiefComplaint |
Text
Describes the primary reason, in the patient's words, for the encounter/visit. This field contrasts with the reasonForVisit, which is the clinician's assessment of the reason for the encounter/visit.
|
0..1
| N/A
|
encounterBillingType |
Concept
Describes the encounter in terms of evaluation and management (e.g., diagnosis or procedure associated with the encounter). For example, Maintenance visit, 5 minutes or less.
|
0..1
| N/A
|
financialClass |
Concept
"Contains the financial class(es) assigned to the patient for the purpose of identifying sources of reimbursement." - HL7 Version 2.8, PV1-20 Note that HL7 does not suggest any values for this code (in User-defined Table 64).
|
0..1
| N/A
|
hospitalService |
Concept
"Contains the treatment or type of surgery that the patient is scheduled to receive." - HL7 Version 2.8, PV1-10. Possible Values (from HL7 Table 69) include: Cardiac Service, Medical Service, Pulmonary Service, Surgical Service, Urology Service.
|
0..1
| N/A
|
isEmploymentRelated |
Concept
"Specifies whether a patient's illness was job-related." - HL7 Version 2.8, PV2-15
|
0..1
| N/A
|
modeOfArrival |
Concept
] Identifies the mode of transportation of the patient’s arrival, for example, ambulance, car, walking etc.
|
0..1
| N/A
|
patientType |
Concept
"Contains site-specific values that identify the patient type." - HL7 Version 2.8, PV1-18 Note that HL7 does not suggest any values for this code (in User-defined Table 18).
|
0..1
| N/A
|
previousServiceDate |
TemporalValue
"Contains the date of previous service for the same recurring condition. This may be a required field for billing certain illnesses (e.g., accident related) to a third party." - HL7 Version 2.8, PV2-14.
|
0..1
| N/A
|
publicityCode |
Concept
"Contains a user-defined code indicating what level of publicity is allowed for a specific visit." - HL7 Version 2.8, PV2-21. Possible values include (from HL7 V2 Table 215): Family only; No Publicity; Other; Unknown.
|
0..1
| N/A
|
reasonForVisit |
List<Concept>
The reason for the encounter/visit from the clinician's point of view. This field contrasts with the chiefComplaint, which is the patient's description of the reason for the encounter/visit.
|
0..1
| 0..*
|
referralSource |
Concept
Identifies the source of the admission or encounter. In other words, identified where the patient was before being sent for this encounter. Possible values include: Community, Other facility, etc.
|
0..1
| N/A
|
servicingFacility |
Concept
"This field is used in a multiple facility environment, e.g., multiple campuses or buildings, to indicate the healthcare facility with which this visit is associated." - HL7 Version 2.8, PV1-39. Note that HL7 does not suggest any values for this code (in User-defined Table 115).
|
0..1
| N/A
|
specialArrangements |
List<Concept>
A set of values representing the types of special arrangements provided or to be provided for this patient encounter (e.g., wheelchair, stretcher, interpreter, attendant, seeing eye dog)
|
0..1
| 0..*
|
specialCourtesy |
List<Concept>
"Indicates whether the patient will be extended certain special courtesies." - HL7 Version 2.8, PV1-22. Note that HL7 does not suggest any values for this code (in User-defined Table 45).
|
0..1
| 0..*
|
triageNotes |
List<Annotation>
Triage notes for the patient visit. Added for Public Health Reporting Initiative.
|
0..1
| 0..*
|
assignedPatientLocation |
Location
"This field contains the patient's initial assigned location or the location to which the patient is being moved. The first component may be the nursing station for inpatient locations, or clinic or department, for locations other than inpatient. For canceling a transaction or discharging a patient, the current location (after the cancellation event or before the discharge event) should be in this field." - HL7 Version 2.8, PV1-3
|
0..1
| N/A
|
pendingLocation |
Location
"Indicates the point of care, room, bed, healthcare facility ID, and bed status to which the patient may be moved. The first component may be the nursing station for inpatient locations, or the clinic, department, or home for locations other than inpatient." - HL7 Version 2.8, PV1-42
|
0..1
| N/A
|
serviceDeliveryLocation |
Location
"The location to which the patient is assigned. It is a role played by a place at which services may be provided. Note that a single physical place can play multiple service delivery location roles each with its own attributes. For example, a Podiatry clinic and Research clinic may meet on alternate days in the same physical location; each clinic uses its own mailing address and telephone number." (HL7)
|
0..1
| N/A
|
temporaryLocation |
Location
"Contains a location other than the assigned location required for a temporary period of time (e.g., OR, operating theatre, etc.)." - HL7 Version 2.8, PV1-11
|
0..1
| N/A
|
priorTemporaryLocation |
List<Location>
"This field is used to reflect the patient's temporary location (such as the operating room/theatre or x-ray) prior to a transfer from a temporary location to an actual location, or from a temporary location to another temporary location. The first component may be the nursing station for inpatient locations, or the clinic, department, or home for locations other than inpatient." - HL7 Version 2.8, PV1-43
|
0..1
| 0..*
|
origin |
Location
The location from which the patient came before admission
|
0..1
| N/A
|
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.
|
0..1
| N/A
|
confidentialityCode |
Concept
Contains a set of values that control the disclosure of information about this patient
|
0..1
| N/A
|
length |
Duration
Quantity of time the encounter lasted. This excludes the time during leaves of absence.
|
0..1
| N/A
|
encounterClass,
encounterType,
period,
status,
partOf,
diagnosis
identifier,
subjectOfInformation,
additionalText,
recordStatus,
recorded,
signed,
cosigned,
verified
archetype_node_id,
name,
archetype_details