Files > OUTPATIENT ENCOUNTER

name

OUTPATIENT ENCOUNTER

number

409.68

location

^SCE(

description

This file contains all outpatient encounters since 10/1/93 that have been successfully checked out or need to be checked out. The types of encounters that caused entries to be added to this file are appointments, add/edit stop codes and dispositions. If the encounter needs to be checked out then it will have a status of 'PENDING ACTION'. The site will not receive workload credit if the status remains 'PENDING ACTION'. 'PENDING ACTION' includes both 'ACTION REQUIRED' and 'NO ACTION TAKEN' statuses. If the encounter has been no-showed or cancelled then it will NOT be in this file. Inpatient encounters will always have a status of 'INPATIENT APPOINTMENT'. Appointments made for non-count clinics will always have a status of 'NON-COUNT'. All other encounters will have a status of 'CHECKED OUT'.

Fields

#	Name	Location	Type	Details	Index	Description
.01	date(+)	0;1	DATE-TIME		B	This field contains the date and time when outpatient encounter occurred.
.02	patient(+)	0;2	POINTER	2	C	This field contains the patient associated with the encounter.
.03	clinic stop code(+)	0;3	POINTER	40.7		This field contains the CLINIC STOP CODE associated with the outpatient encounter.
.04	location	0;4	POINTER	44		This field contains the location, usually a clinic, where the encounter took place. This field is optional.
.05	visit file entry	0;5	POINTER	9000010	AVSIT	This field indicates the VISIT file entry associated with this encounter. This field is optional and will only be filled in if the site is running the Visit Tracking module.
.06	parent encounter	0;6	POINTER	409.68	APAR	This field associates the current encounter with a parent encounter. For example, if there are add/edit stop codes associated with an appointment, then all the add/edit encounter entries will have this parent field filled in with the appointment encounter. This relationship allows the check out software to use the check out information of the appointment for the add/edits, as well.
.07	check out process completion	0;7	DATE-TIME			This field indicates the check out process has been successfully completed for this outpatient encounter.
.08	originating process type(+)	0;8	SET OF CODES	1:APPOINTMENT 2:STOP CODE ADDITION 3:DISPOSITION 4:CREDIT STOP CODE		This field indicates the type of process that created this encounter. The types are the follwoing: 1 - appointment 2 - add/edit stop code 3 - disposition
.09	extended reference	0;9	FREE TEXT			This field indicates the internal multiple entry of the originating process that created the encounter. The reference mapping is the following: Originating Process Global Reference ------------------- ---------------- 1 - appointments ^SC(,"S",,1,) Note: If this field is equal to 999999, it means that the appointment encounter was created by the ACRP Database Conversion functionality in patch SD*5.3*211. The 999999 indicates that the above ^SC node did not exist at the time of the conversion. The node did not exist because it had been purged. The conversion set and then killed the psuedo 999999 node in order to create the encounter. As a result, the 999999 also means that the ELIGIBILITY OF ENCOUNTER (#.13) for the encounter was the patient's primary eligibility at the time of the conversion, since no history exists. 2 - add/edits Always null ; not applicable 3 - dispositions ^DPT(,"DIS",)
.1	appointment type(+)	0;10	POINTER	409.1		This field contains the appointment type assoicated with the outpatient encounter.
.11	medical center division(+)	0;11	POINTER	40.8		This field indicates the medical center division where the encounter took place.
.12	status	0;12	POINTER	409.63		This field indicates the status of the encounter. Currently, the only possible statuses are the following: CHECKED OUT PENDING ACTION INPATIENT APPOINTMENT NON-COUNT Future, no-showed and cancelled appointments are not included in this file at the present time.
.13	eligibility of encounter(+)	0;13	POINTER	8		This field contains the eligibility associated with the encounter.
.2	unique visit number	0;20	FREE TEXT			This is the unique visit ID created by PCE. It is stored for every encounter. This number will be obtained from a supported call provided by PCE.
101	edited last by	USER;1	POINTER	200		This field records the user who last edited the entry.
102	date/time last edited	USER;2	DATE-TIME			This field contains the date/time that the entry was last edited.
103	created by	USER;3	POINTER	200		This field records the user who created the entry.
104	date/time created	USER;4	DATE-TIME			This field contains the date/time that the entry was made.
201	computer generated?	CG;1	BOOLEAN	0:NO 1:YES		This field is used for data validation. It helps determine which entries were automatically generated by outside packages. This field should not be editied.
202	unresolved appt type reason	CG;2	SET OF CODES	1:DUAL ELIGIBILITY 2:POSSIBLE COMP & PEN		If visit has an appointment type of computer generated, the UNRESOLVED APPT TYPE REASON field will also be stuffed with the best possible reason why an appropriate appointment type could not be determined. Currently, if a patient has a comp and pen exam within the last three days of the visit date which is computer generated the unresolved reason will be POSSIBLE COMP & PEN. If a patient has a dual eligibility and one of those eligibilities is Sharing Agreement, Employee, or Collateral, the unresolved reason will be DUAL ELIGIBILITY. If there is a scenario where both apply, the default is POSSIBLE COMP & PEN.
901	created by conversion	CNV;1	BOOLEAN	0:NO 1:YES		This field is set to 'Yes' if the encounter is created by the ACRP Database Conversion patch (SD*5.3*211).
902	original create dt from 'sdv'	CNV;2	DATE-TIME			If this encounter was created by the ACRP Database Conversion patch (SD*5.3*211) from an entry in the SCHEDULING VISITS (#409.5) file then this field contains the date that the original entry in the SCHEDULING VISITS file was created.
903	non-historical stop code used	CNV;3	BOOLEAN	0:NO 1:YES		This field is set to "YES" if this encounter was created by ACRP Database Conversion patch (SD*5.3*211) and the stop code associated with the encounter was obtained from the HOSPITAL LOCATION (#44) file entry for the clinic at the time of the conversion. In other words, there was no mechanism available to absolutely determine the historical value of either a clinic stop code or a credit stop code for a clinic at the time the encounter actually occurred.
904	conversion completed	CNV;4	BOOLEAN	0:NO 1:YES		This field indicates whether or not the conversion process has been completed for this encounter.
905	date of last conversion	CNV;5	DATE-TIME			This is the date that the conversion process was last completed for this encounter.