| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | account reference(+) | 0;1 | NUMERIC | The number by which all VistA applications will reference an external medical billing system account number for purposes of attaching charges for 1st or 3rd party billing. | ||
| .02 | external account number | 0;2 | FREE TEXT | C | The number provided by the external medical billing system for purposes of attaching charges for 1st or 3rd party billing. | |
| .03 | patient(+) | 0;3 | POINTER | 2 | The Patient identifier associated with the billing account. An internal entry number to the PATIENT file (#2). | |
| .04 | application reference | 0;4 | FREE TEXT | This field value indicates where in application processing the GETACCT^IBBAPI function is called. | ||
| .05 | external acct rec'd | 0;5 | DATE-TIME | The date/time at which the External Account Number was received and processed into file #375, field #.02. | ||
| .2 | test patient | 0;20 | BOOLEAN | 1:YES | If the DFN for this patient indicates a test patient as a result of a call to $$TESTPAT^VADPT, then this field is set to "YES". | |
| 1.02 | patient class(+) | PV1;2 | SET OF CODES | I:INPATIENT O:OUTPATIENT | The Patient associated with this account is classified as either "I" (Inpatient) or "O" (Outpatient). | |
| 1.03 | patient location | PV1;3 | POINTER | 44 | The sending application provides a pointer to the HOSPITAL LOCATION file (#44), which provides the a medical center location where the patient visit took place or where service was provided. | |
| 1.04 | appointment type | PV1;4 | POINTER | 409.1 | If the account is setup for an actual outpatient visit (i.e., a Scheduled appointment), this field will contain a pointer to the APPOINTMENT TYPE file (#409.1). | |
| 1.07 | attending physician | PV1;7 | POINTER | 200 | The sending application may provide data on the Attending Physician or Ordering Provided as a pointer to the NEW PERSON file (#200). | |
| 1.09 | consulting physician | PV1;9 | POINTER | 200 | The sending application may provide data on the Consulting Physician related to a patient visit as a pointer to the NEW PERSON file (#200). | |
| 1.1 | purpose of visit | PV1;10 | SET OF CODES | 1:C&P 2:10-10 3:SV 4:UV | This field may contain a code to indicate the general type of the outpatient visit associated with this account: C&P = Compensation & Pension 10-10 = Registration 10-10 SV = Scheduled Visit UV = Unscheduled Visit. | |
| 1.17 | admitting physician | PV1;17 | POINTER | 200 | The sending application may provide data on the Admitting Physician, Surgeon, or Primary Provider associated with the visit/encounter. The data is provided as a pointer to the NEW PERSON file (#200). | |
| 1.18 | primary stop code | PV1;18 | POINTER | 40.7 | The sending application may provide a pointer to the CLINIC STOP file (#40.7) in order to identify the Primary Stop Code associated with the visit, encounter, or occasion of service. | |
| 1.25 | check-in date/time | PV1;25 | DATE-TIME | Normally only used when SCHEDULING is the sending application, this indicates the date/time of the clinic visit check-in. | ||
| 1.41 | credit stop code | PV1;41 | POINTER | 40.7 | The sending application may provide a pointer to the CLINIC STOP file (#40.7) in order to identify the Credit Stop Code associated with the visit, encounter, or occasion of service. | |
| 1.44 | admit date/time | PV1;44 | DATE-TIME | The definition of this data element is dependent upon the application that is the originating source of the data in the account record. SCHEDULING -- Appointment Date/Time PCE -- Visit Date/Time PTF/FEE BASIS -- Admit Date RADIOLOGY -- Date Exam Desired PROSTHETICS -- Entry Date OP PHARMACY -- Fill/Refill Date SURGERY -- Date of Operation | ||
| 1.45 | discharge date/time | PV1;45 | DATE-TIME | Used only by Scheduling to indicate the Check-Out Date/Time for the outpatient appointment. | ||
| 1.5 | alternate visit id | PV1;50 | FREE TEXT | Radiology Secondary Visit Number; used for Radiology charges; the external billing system's Visit Number associated with the CPRS ORDER (#100) for the outpatient or inpatient Radiology order. Concatenate ";;;;RAD to numeric string. Surgery Surgical Case Number; used for Surgery account creation. Concatenate ";;;;SUR to numeric string. OP Pharmacy IEN to PRESCRIPTION file (#52); used for Pharmacy account creation. Concatenate ";;;;OPP to numeric string. | ||
| 1.51 | workload non-count | PV1;51 | SET OF CODES | Y:WNC N:WC | Normally only used when SCHEDULING is the sending application, this defines the clinic location found in field #1.03 as "count" or "non-count" for workload purposes. | |
| 1.52 | other provider | PV1;52 | POINTER | 200 | Data for an additional Provider to be supplied by the calling application as a pointer to the NEW PERSON file (#200). | |
| 2.07 | eligibility of visit | PV2;7 | POINTER | 8.1 | Only used by SCHEDULING or PCE to indicate the patient's Eligibility related to the outpatient visit with which this account record is associated. Data is provided as a pointer to the MAS ELIGIBILITY CODE file (#8.1). | |
| 2.08 | expected admit date/time | PV2;8 | DATE-TIME | The definition of this data element is dependent upon the application that is the originating source of the data. SCHEDULING -- Appointment Date/Time PROSTHETICS -- Entry Date/Time SURGERY -- Planned Date of Operation RADIOLOGY -- Date Desired for Exam | ||
| 2.24 | appointment status | PV2;24 | SET OF CODES | R:SCHEDULED/KEPT I:INPATIENT NS:NO-SHOW NSR:NO-SHOW/RESCHEDULED CP:CANCELLED BY PATIENT CPR:CANCELLED BY PATIENT/RESCHEDULED CC:CANCELLED BY CLINIC CCR:CANCELLED BY CLINIC/RESCHEDULED NT:NO ACTION TAKEN | ||
| 2.46 | pt status effective date | PV2;46 | DATE-TIME | The definition of this data element is dependent upon the application that is the originating source of the data. SCHEDULING - Date Appointment Made. PROSTHETICS - Date Ordered/Suspense Date. | ||
| 3.03 | procedure code | PR1;3 | POINTER | 81 | The applications sending account data to IBB may provide a purpose for the visit, encounter, or occasion of service, in the form of a pointer value to the CPT file (#81). The pointer is used to derive a specific CPT or HCPCS code. | |
| 3.06 | functional type | PR1;6 | FREE TEXT | Radiology - Imaging Type Abbreviation. ANI = ANGIO/NEURO/INTERVENTIONAL CARD = CARDIOLOGY STUDIES (NUC MED) CT = CT SCAN RAD = GENERAL RADIOLOGY MRI = MAGNETIC RESONANCE IMAGING MAM = MAMMOGRAPHY NM = NUCLEAR MEDICINE US = ULTRASOUND VAS = VASCULAR LAB Prosthetics - Prosthetics Flag. O = Home Oxygen P = Purchasing I = Stock Issue | ||
| 3.11 | surgeon | PR1;11 | POINTER | 200 | If SURGERY passes to IBB data for setup of an account, then this field provides the identity of the Principal Surgeon as a pointer to the NEW PERSON file (#200). | |
| 3.16 | procedure code modifier(s) | PR1;16 | FREE TEXT | Data may only be contained here if field #3.03 holds a pointer to the CPT file (#81), which may be resolved to a CPT or HCPCS code. A string of numbers delimited by semi-colons; each number is a pointer to the CPT MODIFIER file (#81.3). Example: 68;245;74;318; | ||
| 4 | diagnosis | DG1;0 | MULTIPLE | 375.04 | Multiple DG1 Segments are allowed within an ADT message. Each subrecord in subfile #375.04 contains data for an individual DG1 Segment. | |
| 5 | sc/ei classification | ZCL;0 | MULTIPLE | 375.05 | Multiple ZCL Segments are allowed within an ADT message. Each subrecord in subfile #375.05 contains data for an individual ZCL Segment. | |
| 11 | procedure text | 11;1 | FREE TEXT | If the application calling GETACCT^IBBAPI does not yet have Procedure data as a pointer to the CPT file (#81), then Procedure may be supplied as free text. The calling application may also provide data for this field that is used to enhance or add detail to the CPT or HCPCS code provided in field #3.03. | ||
| 12 | diagnosis text | 12;1 | FREE TEXT | If the application calling GETACCT^IBBAPI does not yet have Diagnosis data as a pointer to the ICD DIAGNOSIS file (#80), then Diagnosis may be supplied as free text. | ||
| 13 | facility id | 13;1 | POINTER | 40.8 | Identifies the facility (i.e., medical center division) associated with the patient service. | |
| 14.01 | surgical case # | 14;1 | POINTER | 130 | Surgical Case # for any account setup by Surgery package. | |
| 14.02 | surgical specialty | 14;2 | POINTER | 45.3 | Surgical Specialty for any account setup by Surgery package. | |
| 15.01 | radiology clinical hx | 15;1 | POINTER | 75.1 | The Clinical History for the Radiology exam can be obtained by using this pointer value to the RAD/NUC MED ORDERS file (#75.1). | |
| 16.01 | outside location | 16;1 | FREE TEXT | If the Patient Location for the visit/encounter/service is outside the VAMC, then the name of that location is stored here as free text. For A01 event messages related to inpatient admissions to outside hospitals, the PTF application will use "FEE BASIS" as a generic location descriptor. | ||
| 99 | event history | 99;0 | MULTIPLE | 375.099 | This subfile stores a history of the HL7 ADT events that are sent/received for this PFSS ACCOUNT record. |