| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | date/time(+) | 0;1 | DATE-TIME | B | Enter in this field the date/time of the movement (admission, transfer, discharge, treating specialty transfer, lodger check-in, or lodger check- out). Time must be included. | |
| .02 | transaction(+) | 0;2 | POINTER | 405.3 | Enter in this field the transaction type of the movement. Choose from: 1 ADMISSION 2 TRANSFER 3 DISCHARGE 4 CHECK-IN LODGER 5 CHECK-OUT LODGER 6 SPECIALTY TRANSFER | |
| .03 | patient(+) | 0;3 | POINTER | 2 | C | Enter the patient for which this movement occurred. This field is a pointer to the PATIENT file. |
| .04 | type of movement(+) | 0;4 | POINTER | 405.1 | Choose the type of movement this patient had. You will be selecting from active FACILITY MOVEMENT TYPES for which the TRANSACTION TYPE of this movement matches the TRANSACTION TYPE of the FACILITY MOVEMENT TYPE. For example, if you are admitting a patient, you will only be able to select active admission types. | |
| .05 | transfer facility(+) | 0;5 | POINTER | 4 | If this movement is a TRANSFER IN (admission from another facility), TRANSFER OUT (discharge to another facility), or an ASIH movement to another facility (TO ASIH (OTHER FACILITY), for example), you will be prompted for TRANSFER FACILITY and will be asked to choose from an entry in the INSTITUTION file. This field is required for those movement types mentioned above. | |
| .06 | ward location(+) | 0;6 | POINTER | 42 | Enter in this field the WARD to which this patient is being admitted or transferred to. Choose from ACTIVE entries in the WARD LOCATION file. This field will only be prompted for movements to WARDS at the home facility. | |
| .07 | room-bed | 0;7 | POINTER | 405.4 | Select the ROOM-BED to which you are admitting or transferring this patient. Select from those ACTIVE beds in the ROOM-BED file which are assigned to the WARD LOCATION chosen for this movement. | |
| .08 | primary physician | 0;8 | POINTER | 200 | Enter the healthcare provider with primary responsibility for the direct care of the patient. This may be the resident or intern in a teaching facility or the staff physician in a nonaffiliated hospital. This field will only be prompted for movements with a transaction type of 'specialty transfer'. | |
| .09 | facility treating specialty(+) | 0;9 | POINTER | 45.7 | When entering a movement with a TRANSACTION TYPE of SPECIALTY CHANGE, you will be asked to provide the treating specialty assigned to this patient. Choose an entry from the FACILITY TREATING SPECIALTY file which best describes the care this patient is receiving. | |
| .1 | diagnosis [short](+) | 0;10 | FREE TEXT | When admitting a patient, you will be asked to provide a brief desciption of the diagnosis of this patient upon admission. | ||
| .11 | admitted for sc condition? | 0;11 | BOOLEAN | 1:YES 0:NO | Is this patient being admitted for a service connected condition? | |
| .12 | admitting regulation(+) | 0;12 | POINTER | 43.4 | When admitting a patient, you must choose an active ADMITTING REGULATION which best describes the category under which this patient is being admitted. | |
| .13 | absence return date | 0;13 | DATE-TIME | If the patient is being transferred to an absence status (via the AUTH ABSENCE 96 HOURS OR LESS or AUTHORIZED ABSENCE transfer types), you will be asked to provide the date this patient is expected to return. If you choose to transfer the patient with AUTH ABSENCE 96 HOURS OR LESS, this date must be less than or equal to 4 days from the date of transfer. If you choose to transfer the patient AUTHORIZED ABSENCE, the date of return most be more than 4 days after the date of transfer. | ||
| .14 | admission/check-in movement(+) | 0;14 | POINTER | 405 | CA | This field is a pointer to the admission or check-in lodger movement which is associated with the transaction being entered. |
| .15 | asih admission(+) | 0;15 | POINTER | 405 | This field is set internally by the module. If a patient is transferred either TO ASIH FROM NHCU/DOM or CONTINUED ASIH, this field will point to the entry in this file which holds the admission created by the module. | |
| .16 | ptf entry | 0;16 | POINTER | 45 | APTF | This field is used for movements with a TRANSACTION TYPE of admission only. It stores the internal entry number of the record in the PTF file. |
| .17 | discharge/check-out movement | 0;17 | POINTER | 405 | Pointer to the discharge or check-out movement associated with this admission or check-in. If not defined, the patient is still in-house. | |
| .18 | mas movement type(+) | 0;18 | POINTER | 405.2 | This field is internally set by the module. When you enter a FACILITY MOVEMENT TYPE (field .04 of this file), this field will automatically be set to the internal number of the MAS-distributed movement type to which this FACILITY MOVEMENT TYPE points. This internal number is used throughout the code of MAS and various other packages to determine the flow of processing that should occur. | |
| .19 | attending physician(+) | 0;19 | POINTER | 200 | Enter the supervising physician who is responsible for the care of the patient. Nonaffiliated hospitals may choose not to use this field. This field will be prompted for movements with a transaction type of 'specialty change' only. | |
| .2 | admitting eligibility(+) | 0;20 | POINTER | 8 | This field will be used in a future version to track the eligibility of a patient upon admission. This information will be used in the VISIT file which is being developed for use in DoD facilities. | |
| .21 | asih transfer(+) | 0;21 | POINTER | 405 | This field is internally set by the module. If the MAS MOVEMENT TYPE of this movement is TO ASIH, this field will contain a pointer to the transfer movement that created this admission (either a TO ASIH transfer or a CONTINUED ASIH transfer). | |
| .22 | asih sequence(+) | 0;22 | NUMERIC | This field is used internally by the module for movements that are ASIH. When transferring a patient ASIH to your own facility, there are 2 movements created at the same date/time (the admission and the transfer). This is also true for discharges FROM ASIH where both a discharge and a transfer occur at the same date/time. The movement that physically occurs first (the transfer in the first example, and the discharge in the second) will have a sequence number of 1 while the subsequent movement will have a sequence number of 2. This number (divided by 100000000) will be added to the date/time of the movement to aid in cross-referencing these movements. This is intended to make code generation quicker. [NOTE: non- ASIH movements will have a ASIH SEQUENCE of 0] | ||
| .23 | dmms episode number | 0;23 | NUMERIC | This field has been added for use by the DMMS package. It will hold the episode number of the movement as defined internally by that package. | ||
| .24 | related physical movement | 0;24 | POINTER | 405 | APHY | This field will be stored for movements with a TRANSACTION TYPE of TREATING SPECIALTY only. If the treating specialty transfer is in conjunction with a physical movement (either an admission or a transfer), this field will contain a pointer to that physical movement. |
| .25 | scheduled admission? | 0;25 | BOOLEAN | 1:YES 0:NO | If this admission was a result of a previously scheduled admission, this field should be answered yes. This field will be filled in for movements with a TRANSACTION of ADMISSION only. | |
| .26 | ptf purge status | 0;26 | SET OF CODES | 1:PURGED 0:ACTIVE | ||
| .27 | visit file entry | 0;27 | POINTER | 9000010 | AVISIT | |
| 30.01 | reason for lodging(+) | LD;1 | POINTER | 406.41 | Enter the reason this patient was lodged (inclement weather, traveling distance, etc.). | |
| 30.02 | lodging comments | LD;2 | FREE TEXT | Enter an additional comment on why this patient is being lodged if you wish. | ||
| 30.03 | disposition(+) | LD;3 | SET OF CODES | a:ADMITTED d:DISMISSED | Enter in this file the disposition of this patient upon being checked-out as a lodger. Choose from ADMITTED (if the patient was admitted to your facility) or DISMISSED (if the patient was returned to his place of residence). | |
| 40 | exclude from facility dir | COMPUTED | This computed field will determine if the patient wished to be excluded from the Facility Directory for the corresponding admission. | |||
| 41 | facility directory exclusion | DIR;1 | BOOLEAN | 0:NO 1:YES | Denotes whether or not the patient wished to be excluded from the Facility Directory for this admisison. The Facility Directory is the directory of current inpatients in the facility. If the patient wishes to be excluded from the Facility Directory, then the VAMC can not make a positive statement to family, friends, or others as to whether the patient is here or not. | |
| 42 | facility directory time stamp | DIR;2 | DATE-TIME | Date/time answer to Facility Directory exclusion question was entered. | ||
| 43 | facility directory user | DIR;3 | POINTER | 200 | User entering the patient's response to the Facility Directory exclusion question. | |
| 51 | source of admission | COMPUTED | This computed field will determine the SOURCE OF ADMISSION for the corresponding admission. The value is obtained from the PTF entry associated with the admission. This field is only computed for admission entries. If is field is needed while working with another type of movement, the following extended syntax can be used: ADMISSION/CHECK-IN MOVEMENT:SOURCE OF ADMISSION | |||
| 52 | ptf movement number | PTF;2 | NUMERIC | This field may be filled in for treating specialty movements. It will only be filled in if the treating specialty movement causes a PTF 501 movement to be created in the PTF record associated with the admission. The number stored in this field will be the internal multiple entry number of the 501 multiple in that PTF record. This field is updated automatically and no user input is necessary. | ||
| 53 | next ptf movement | PTF;3 | NUMERIC | This field may be filled in for treating specialty movements. It will only be filled in if the treating specialty movement causes a PTF 501 movement to be created in the PTF record associated with the admission. The number stored in this field will be the internal multiple entry number of the 501 multiple, in that PTF record, corresponding to the next chronological 501 movement, if one exists. This field is updated automatically and no user input is necessary. | ||
| 54 | admitting category | PTF;4 | POINTER | 35.2 | If and entry for the Admitting Regulation exist in the Sharing Agreement Category file (#35.1) then the user will be prompted for the category associated with the Admitting Regulation. | |
| 55 | eligibility | COMPUTED | ||||
| 60.01 | irt background job run | IRT;1 | DATE-TIME | This field stores the date that the IRT background job was run for this admission. If this field contains a date, this admission has been initialized and all standard deficiencies have been created for this admission. When the IRT background Job is run for all admission it will check to see if the admission has already been initialized. If so, this admission will not created duplicate entries for the standard deficiencies. | ||
| 99 | diagnosis | DX;0 | WORD-PROCESSING | Enter an in-depth description of the diagnosis for this patient. This will be asked for movements with a TRANSACTION TYPE of SPECIALTY TRANSFER only. | ||
| 100 | entered by(+) | USR;1 | POINTER | 200 | This field stores the name of the user entering this patient movement. | |
| 101 | entered on(+) | USR;2 | DATE-TIME | This field stores the date/time on which this PATIENT MOVEMENT FILE entry was initially entered. | ||
| 102 | last edited by(+) | USR;3 | POINTER | 200 | This is the user who last edited this patient movement entry. The user is only stored when a change is made. | |
| 103 | last edited on(+) | USR;4 | DATE-TIME | This is the date/time this movement was last edited. It will only be stored if a change was made. | ||
| 200 | ward at discharge | COMPUTED | This computed field will determine the ward that the patient was on when the patient was discharged. This field is only computed for discharge entries. If is field is needed while working with another type of movement, the following extended syntax can be used: ADMISSION/CHECK-IN MOVEMENT:DISCHARGE/CHECK-OUT MOVEMENT:WARD AT DISCHARGE | |||
| 201 | length of stay | COMPUTED | This field will print the length of stay in days from admission to discharge minus DAYS ABSENT and ASIH DAYS. This field is accessible with extended syntax via the following statement: ADMISSION/CHECK-IN MOVEMENT:LOS | |||
| 202 | pass days | COMPUTED | This field will print AUTHORIZED ABSENCE DAYS <96 for each admission episode and is only calculated from the admission movements. This field is accessible with the following extended syntax: ADMISSION/CHECK-IN MOVEMENT:PASS DAYS | |||
| 203 | days absent | COMPUTED | This field is computed to print the number of absence days for a specific admission episode. It will not print PASS DAYS and is calculated from the admission movements only. This field is accessible with the following extended syntax: ADMISSION/CHECK-IN MOVMEMENT:DAYS ABSENT | |||
| 204 | asih days | COMPUTED | This computed field will print the number of ASIH days for a DOM or NHCU admission episode. It will only be calculated from the admission movements that could have ASIH days. This field is accessible with the following extended syntax: ADMISSION/CHECK-IN MOVEMENT:ASIH DAYS | |||
| 300 | original admission date | ORG;1 | DATE-TIME | This field contains the original admission date/time for a patient. | ||
| 11500.01 | ods at admission | ODS;1 | BOOLEAN | 1:YES 0:NO | Was this patient admitted for care due to injuries sustained in Operation Desert Shield? If the patient's period of service is 6 when admitted, this field will automatically be set to 1. | |
| 11500.02 | non-va facility? | ODS;2 | BOOLEAN | 1:YES 0:NO | Respond yes if you are transferring this patient out to a non-VA facility. Respond no if transferring the patient to another VA facility. | |
| 11500.03 | at va expense? | ODS;3 | BOOLEAN | 1:YES 0:NO | Answer yes if this transfer to a non-VA facility is at the VA's expense. | |
| 11500.04 | ods admission entry | ODS;4 | POINTER | 11500.2 | AODSA | If this patient was admitted with a period of service of 6 (ODS), enter the ODS ADMISSIONS file entry corresponding to this admission. |
| 11500.05 | displaced for ods patient? | ODS;5 | BOOLEAN | 1:YES 0:NO | Enter yes if this patient was transferred out in order to free a bed for an operation desert shield patient. Otherwise, respond no. | |
| 11500.06 | va cost to travel | ODS;6 | NUMERIC | Enter the cost of travel to move this VA patient to a non-VA facility. This question is only asked if the patient was transferred in order to make room for an operation desert shield patient. | ||
| 11500.07 | displaced patient | ODS;7 | POINTER | 11500.3 | AODSD | Enter the entry in the DISPLACED PATIENT file which corresponds to this discharge. |