| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .001 | number | 11 | ||||
| .01 | file entry date(+) | 0;1 | DATE-TIME | B | Date of actual entry of consultation request into the file. Transparent to user. | |
| .02 | patient name(+) | 0;2 | POINTER | 2 | F | This is the Patient who the consult or request was ordered for. Enter the patient's name, or the last four digits of the SSN. |
| .03 | oe/rr file number | 0;3 | POINTER | 100 | AC | This is the internal entry number of the order in the Orders File (100). The consult sends CPRS information about the consult which is stored in File 100. This is the IEN of the consult in that file. |
| .04 | patient location | 0;4 | POINTER | 44 | AL | This is the location of the patient when the consult/request order was placed. |
| .05 | ordering facility | 0;21 | POINTER | 4 | This field contains the number, from file 4, of the institution/hospital that is requesting the consult. This field is mandatory if the consult/ request is being sent to another hospital/institution, so that routing information can be obtained in order to return the results to the sending hospital/institution. | |
| .06 | remote consult file entry | 0;22 | NUMERIC | This is the ^GMR(123, file number of the consult from a foreign database. It is stored here so that when the consult is returned in an HL7 message, it can be located at the sending facility. Also, if the sending facility needs to send updated consult information to the receiving facility, this number will reference the consult number there so that the data can be added/ammended and tracking information can be updated. | ||
| .07 | routing facility | 0;23 | POINTER | 4 | This field will contain the INSTITUTION to which communications and updates regarding this request will be routed. If the request is being requested and performed locally, this field will be blank. | |
| .1 | display text of item ordered | 1.11;1 | FREE TEXT | This is the display text of the item ordered. If the order was placed using a quick order, then the Display text is the text from the Order Dialog File. If the order was placed by selecting an Orderable Item, then the text is the Print Name from the Orderable Item file. | ||
| .125 | ifc role | 12;5 | SET OF CODES | P:PLACER F:FILLER | This field will define the role of the particular VistA system in the fullfillment of the inter-facility consult. This facilitates proper HL7 message formats. PLACER indicates that this VistA system originated and ordered this request. FILLER indicates that this request was generated at the institution in the ORDERING FACILITY field. | |
| .126 | remote ordering provider | 12;6 | FREE TEXT | This field contains the name of the requesting provider of an inter-facility consult. This field is only defined on an inter-facility consult on file at a consulting site. | ||
| .131 | ifc remote service name | 13;1 | FREE TEXT | This field holds the name of the service that will perform the Inter- facility Consult at the remote facility. | ||
| .132 | remote requestor phone | 13;2 | FREE TEXT | This field will contain the telephone number of the remote requestor of an inter-facility consult. This will be displayed with the consult and can expedite communication between requesting provider and consultant. This field is derived from the OFFICE PHONE field of the NEW PERSON file. | ||
| .133 | remote requestor dig pager | 13;3 | FREE TEXT | This field contains the digital pager number of a remote requesting provider if this is an inter-facility consult. This may expedite communication between the requesting provider and the consultant. This data in this field is derived from the DIGITAL PAGER field of the NEW PERSON file. | ||
| 1 | to service(+) | 0;5 | POINTER | 123.5 | C | This is the "TO" service/specialty. This service is responsible for completion of the consult/request. |
| 1.01 | clinical procedure | 1;1 | POINTER | 702.01 | This field contains the CP DEFINITION that is associated with this request. | |
| 2 | from | 0;6 | POINTER | 44 | H | This field represents the location that sent the order to the receiving location. |
| 3 | date of request(+) | 0;7 | DATE-TIME | This is the date and time the order was released from OE/RR. If the TO service entered the order stub through the Add Order (AD) action, this is the service-specified request date. | ||
| 4 | procedure/request type | 0;8 | VARIABLE-POINTER | 101, 123.3 | AP | This is the procedure that was requested via CPRS while ordering. |
| 5 | urgency | 0;9 | POINTER | 101 | This field describes the urgency of the consult. Urgencies are sent in the PROTOCOL File (#101) as: STAT, EMERGENCY, INPATIENT, NEXT AVAILABLE, NOW, ROUTINE, TODAY, WITHIN 24 HOURS, WITHIN 48 HOURS, WITHIN 72 HOURS, WITHIN 1 WEEK, WITHIN 1 MONTH. | |
| 6 | place of consultation | 0;10 | POINTER | 101 | This is the place where the consultation will take place. Choose from: B - Bedside C - Consultant's Choice E - Emergency Room O - On Call EKG - EKG Lab | |
| 7 | attention | 0;11 | POINTER | 200 | Enter the name of a person you would like to alert about the consult. This person will be sent a notification that a new consult exists. In order for the person to see this type of notification, the person must be set up to receive "New service consult" notifications. | |
| 8 | cprs status | 0;12 | POINTER | 100.01 | D | This is the current CPRS status of the consult or request order. The Action Types which may be taken from the "Select Action: " prompt update the status in this file as well as in the Orders File (100). |
| 9 | last action taken | 0;13 | POINTER | 123.1 | This is the last Action Type taken that updated the activity tracking audit trail. | |
| 10 | sending provider | 0;14 | POINTER | 200 | G | This is the provider who originated the order. |
| 11 | result | 0;15 | VARIABLE-POINTER | 691, 691.1, 691.5, 691.6, 691.7, 691.8, 694, 698, 698.1, 698.2, 698.3, 699, 700, 701 | This is a variable pointer used by the GMRC MEDICINE PKG INTERFACE option to associate results in the Medicine Procedure Files with a consult/request order. | |
| 12 | mode of entry | 0;16 | SET OF CODES | 1:SERVICE FORCED ENTRY | When a consult or request is entered by the service, rather than through CPRS order processing, this field will be set to "1" to indicate the Service forced the entry. This forcing means there is no electronic signature related to the order. | |
| 13 | request type(+) | 0;17 | SET OF CODES | C:Consult P:Procedure | This field will indicate whether the order is a consult or procedure request order. Based on this fields value, the Consultation Body Header alters to indicate "Consult Type: " or "Procedure Request: ". | |
| 14 | service rendered as in or out | 0;18 | SET OF CODES | I:inpatient O:outpatient | This field allows the ordering person to indicate if the service is to be rendered on an outpatient or inpatient basis. This is to alleviate the confusion if patient is currently an inpatient/outpatient but is just about to be discharged/admitted and become a outpatient/inpatient. | |
| 15 | significant findings | 0;19 | SET OF CODES | Y:yes N:no U:unknown | If significant findings are noted in the consult results, then this field may be marked "Yes", and appropriate comments may be entered in the "Comment" field. "Unknown" is the default. "No" may also be specified to indicate the results do not include significant findings. | |
| 16 | tiu result narrative | 0;20 | POINTER | 8925 | Pointer to the Text Integration Utilities file (#8925) where consult/request results narrative is stored. | |
| 17 | earliest date | 0;24 | DATE-TIME | |||
| 20 | reason for request | 20;0 | WORD-PROCESSING | This is the reason for requesting the Consult or Procedure Request. | ||
| 30 | provisional diagnosis | 30;1 | FREE TEXT | This is the Provisional Diagnosis the ordering clinician would specify on the Consult Form 513. | ||
| 30.1 | provisional diagnosis code | 30.1;1 | FREE TEXT | This field is used to store the coded portion of the Provisional Diagnosis if a coded diagnosis is sent via CPRS. | ||
| 30.2 | provisional diagnosis date | 30.1;2 | DATE-TIME | This is the date of the provisional diagnosis and will contain a value if the request is filed with a coded diagnosis. This field is used internally to help identify if a given code is active. | ||
| 30.3 | provisional diagnosis system | 30.1;3 | FREE TEXT | This is the 3-character Source Abbreviation (SAB) for the coding system to which a given diagnosis code belongs. This field will only contain a value when a given service is configured to receive a coded diagnosis. This field is used internally to check if a given code is active. For example, ICD is stored if the coding system is ICD-9. 10D is stored if the coding system is ICD-10. | ||
| 40 | request processing activity | 40;0 | MULTIPLE | 123.02 | Maintains history of processing actions. | |
| 50 | associated results | 50;0 | MULTIPLE | 123.03 | ||
| 51 | remote results | 51;0 | MULTIPLE | 123.051 | ||
| 70 | administrative | 70;1 | BOOLEAN | 0:NO 1:YES | This field is set via a trigger on TO SERVICE which will set this field to the value found in the ADMINISTRATIVE field of the REQUEST SERVICES file (#123.5). Requests marked as administrative shall be excluded from the Consults Performance Monitor report [GMRC RPT PERF MONITOR] |