Difference between revisions of "FILE 2"
DavidWhitten (talk | contribs) |
DavidWhitten (talk | contribs) |
||
Line 1: | Line 1: | ||
− | == [[File | + | == [[File 1|File Of Files]] Entry == |
<pre> | <pre> | ||
NUMBER: 2 NAME: PATIENT | NUMBER: 2 NAME: PATIENT | ||
Line 18: | Line 18: | ||
The [[FILE 2|PATIENT File]] contains all the patients followed by the medical center/Outpatient clinic. At a minimum each patient entry must have a NAME, DATE OF BIRTH and SOCIAL SECURITY NUMBER. In order to add a new patient to the [[FILE 2|PATIENT File]] the user must also indicate whether or not the patient is requesting to receive care as a VETERAN of the U.S. Armed Forces and specify the TYPE of patient being added to the system. For the most part the information contained in this [[file~|file]] is demographic in nature, i.e., address, employment, service history, etc., however data concerning admissions, appointments,etc., is also stored in this [[file~|File]]. The ADMISSION sub-field is scheduled to be moved into the | The [[FILE 2|PATIENT File]] contains all the patients followed by the medical center/Outpatient clinic. At a minimum each patient entry must have a NAME, DATE OF BIRTH and SOCIAL SECURITY NUMBER. In order to add a new patient to the [[FILE 2|PATIENT File]] the user must also indicate whether or not the patient is requesting to receive care as a VETERAN of the U.S. Armed Forces and specify the TYPE of patient being added to the system. For the most part the information contained in this [[file~|file]] is demographic in nature, i.e., address, employment, service history, etc., however data concerning admissions, appointments,etc., is also stored in this [[file~|File]]. The ADMISSION sub-field is scheduled to be moved into the | ||
− | new [[FILE 405|PATIENT MOVEMENT File]] by the end of calendar year 1989. Care should be used when removing a patient from the [[FILE 2|PATIENT File]] since virtually all other [[DHCP~|DHCP]] modules do utilize data from this [[file~| | + | new [[FILE 405|PATIENT MOVEMENT File]] by the end of calendar year 1989. Care should be used when removing a patient from the [[FILE 2|PATIENT File]] since virtually all other [[DHCP~|DHCP]] modules do utilize data from this [[file~|file]]. Of the many fields in the [[file~|File]] you will note that many are preceeded by an asterisk. Those fields are scheduled to be removed from the [[file~|file]] due to either lack of use or replacement by another [[field~|field]]/[[file~|file]] in the next release. |
<pre> | <pre> |
Revision as of 16:38, 16 March 2012
File Of Files Entry
NUMBER: 2 NAME: PATIENT
- APPLICATION GROUP: LR
- PACKAGE NAME (c): LAB SERVICE
- APPLICATION GROUP: RA
- PACKAGE NAME (c): RADIOLOGY/NUCLEAR MEDICINE
- APPLICATION GROUP: PS
- PACKAGE NAME (c): PHARMACY
- APPLICATION GROUP: DG
- PACKAGE NAME (c): REGISTRATION
- APPLICATION GROUP: SD
- PACKAGE NAME (c): SCHEDULING
- APPLICATION GROUP: RT
- PACKAGE NAME (c): RECORD TRACKING
- DESCRIPTION:
The PATIENT File contains all the patients followed by the medical center/Outpatient clinic. At a minimum each patient entry must have a NAME, DATE OF BIRTH and SOCIAL SECURITY NUMBER. In order to add a new patient to the PATIENT File the user must also indicate whether or not the patient is requesting to receive care as a VETERAN of the U.S. Armed Forces and specify the TYPE of patient being added to the system. For the most part the information contained in this file is demographic in nature, i.e., address, employment, service history, etc., however data concerning admissions, appointments,etc., is also stored in this File. The ADMISSION sub-field is scheduled to be moved into the new PATIENT MOVEMENT File by the end of calendar year 1989. Care should be used when removing a patient from the PATIENT File since virtually all other DHCP modules do utilize data from this file. Of the many fields in the File you will note that many are preceeded by an asterisk. Those fields are scheduled to be removed from the file due to either lack of use or replacement by another field/file in the next release.
GLOBAL NAME (c): ^DPT( ENTRIES (c): 441 DD ACCESS (c): @ RD ACCESS (c): d WR ACCESS (c): Dd DEL ACCESS (c): Dd LAYGO ACCESS (c): Dd LOOKUP PROGRAM (c): DPTLK VERSION (c): 5.3 COMPILED CROSS-REFERENCES (c): NO BUILD (c): DG*5.3*77 : DG*5.3*78 : DG*5.3*93 : IB*2.0*63 : DG*5.3*108 : IB*2.0*75 : REGISTRATION PATCHED V 5.3 : IB*2.0*52 : DG*5.3*114 : DG*5.3*121 : DG*5.3*141 : COMPARE REGISTRATION V 5.3 : DG*5.3*91 : DG*5.3*122 : IB*2.0*85 : LR*5.2*153 : DG*5.3*174 : DG*5.3*155 : DG*5.3*184 : DG*5.3*196 : SD*5.3*148 : IB*2.0*102 : DG*5.3*172 : DG*5.3*147 : DG*5.3*177 : OUTPATIENT PHARMACY VERSION 7.0 : DG*5.3*149 : DG*5.3*231 : DG*5.3*232 : DG*5.3*182 : SD*5.3*206 : DG*5.3*269 : IB*2.0*103 : DG*5.3*247 : IB*2.0*126 : DG*5.3*190 : DG*5.3*307 : DG*5.3*329 : SD*5.3*223 : DG*5.3*294 : DG*5.3*314 : DG*5.3*333 : DG*5.3*343 : DG*5.3*361 : IVM*2.0*37 : DG*5.3*392 : DG*5.3*355 : DG*5.3*299 : DG*5.3*342 : DG*5.3*474 : DG*5.3*454 : DG*5.3*415 : DG*5.3*496 : DG*5.3*489 : DG*5.3*498 : DG*5.3*500 : DG*5.3*506 : DG*5.3*244 : COMP OUTPATIENT PHARMACY VERSION 7.0 : DG*5.3*497 : DG*5.3*505 : DG*5.3*477 : IB*2.0*184 : DG*5.3*522 : DG*5.3*528 : DG*5.3*560 : DG*5.3*545 : DG*5.3*602 : DG*5.3*575 : DG*5.3*597 : DG*5.3*451 : IB*2.0*232 : DG*5.3*564 : DG*5.3*485 : DG*5.3*632 : MSCDPT*1.0*18 : MSCDG*1.0*2 : MSCDG*1.0*5 : MSCDPT*1.0*19 : DG*5.3*640 : DG*5.3*665 : DG*5.3*624 : DG*5.3*677 : DG*5.3*631 : DG*5.3*658 : DG*5.3*672 : DVB*4.0*57 : MSCEPI*2.0*1