The PV1 segment contains information about the patient visit. It can be used to send multiple-visit records to the same patient account or single-visit records to more than one account. The following table describes the guidelines that should be observed when interpreting these segment layouts:
| Sequence No. | Destination Data Length | Data Field Name | Comments | ACME Engine Special Processing for Destination | Field Sent to Target Application |
|---|---|---|---|---|---|
|
1 |
Unlimited |
Segment ID |
"PV1" Jamf: Conditional Segment |
Copy |
Yes |
|
2 |
Unlimited |
Patient Class |
Jamf: Ignored Acme IE Std: I = Inpatient O = Outpatient or Observation P = Pre-Admit or Pre-Reg |
Copy if valued |
Yes |
|
3 |
Unlimited |
Assigned Patient Location |
Jamf: Required Used to link visit to a physical location and a specific tablet |
Populate for all outbound messages |
Yes |
|
3.1 |
Unlimited |
Point of Care |
Jamf: Required Acme: Move to PV1.3.3 to provide a custom unique identifier for auto-lookup in Jamf Pro. |
No | |
|
3.2 |
Unlimited |
Room |
Jamf: Required Acme: Move to PV1.3.3 to provide a custom unique identifier for auto-lookup in Jamf Pro. |
No | |
|
3.3 |
Unlimited |
Bed |
Jamf: Requested values for Unit, Room, and Bed to all be populated in this field. |
Copy values from PV1.3.1, PV1.3.2, PV1. 3.3, and PV1.3.4, and concatenate all values into unique string. Separator can be dashes, underscore, or no separator at all, and it cannot be a carrot. For example: CVICU220-2204-A-ACME |
Yes |
|
3.4 |
Unlimited |
Facility |
Jamf: Required Acme: Move to PV1.3.3 to provide a custom unique identifier for auto-lookup in Jamf Pro. |
No | |
|
6 |
Unlimited |
Prior Patient Location |
Jamf: Optional for certain workflows. Used to link visit to a physical location and a specific tablet. |
If mapping workflows to prior patient location, follow concatenation framework from current assigned location (PV1.3) |
Yes |
|
6.1 |
Unlimited |
Point of Care |
Jamf: Optional |
No | |
|
6.2 |
Unlimited |
Room |
Jamf: Optional |
No | |
|
6.3 |
255 |
Bed |
Jamf: Optional |
If mapping workflows to prior patient location, follow concatenation framework from current assigned location (PV1.3). |
Yes |
|
6.4 |
Unlimited |
Facility |
Jamf: Optional |
No |