VistA-internationalization/TranslationSpreadsheets/WV-DIALOG-0414.txt

308 lines
14 KiB
Plaintext

English French Notes Complete/Exclude
Summary for division:
For clinics with credit pair:
For clinics with selected credit pair
For clinics selected by name
SDARR(
Clinic Stop Code Pair:
Detail for clinic:
Ava.
Pct.
Credit Pair
Sch. Wait
Availability Date
Enc.
Appts Time
Days Days
Non-next Available Appointments
Next Ava. 0-1 0-1 2-7 2-7 8-30 8-30 31-60 31-60 >60 >60
Ava. Wait
Days Wait
Appts Time
Next Ava. 0-1 0-1 0-1 2-7 2-7 2-7 8-30 8-30 8-30 31-60 31-60 31-60 >60 >60 >60
Ava. Wait
Days Wait Wait
Appts Time1
Appts Time1 Time2
Ava. Date Wait Wait
Scheduled Patient Name SSN Appointment Date Scheduling Request Type Ind. Desired F/U Time1 Time2
REBOOK DATE
Date extracted:
No appointments scheduled during this date range were found.
Next available
Not-next ava-C/R
Not-next ava-P/R
Walk in appoint
Multi booking
Auto rebook
Not-next available
NOTE: TYPE '0' represents appointments scheduled during the report time frame not indicated by the user or by calculation to be
'next available' appointments. TYPE '1' represents appointments defined by the user as being 'next available' appointments. TYPE
'2' represents appointments calculated to be 'next available' appointments. TYPE '3' represents appointments indicated both by the
user and by calculation to be 'next available' appointments. WAIT TIME is the average number of days from the date an appointment
was scheduled to the date it is to be performed. The '% NNA' and '% NA' columns reflect percentage of appointments scheduled within
30 days for 'non-next available' appointments (types 0 & 2) and 'next available' appointments (types 1 & 3), respectively.
NOTE: The date range categories ('0-1', '2-7', '8-30', etc.) are based on the difference between the 'desired date' defined for the
appointment and the date the appointment was performed. 'Wait Time' reflects the average of this difference for all appointments in
each category. 'Follow up' status is determined by encounter activity to the same DSS ID credit pair as the appointment clinic
within the previous 24 months.
the date the appointment was performed. 'Wait Time2' reflects the average difference between the transaction date (the date the
appointment was entered by the Scheduling package user) and the date the appointment was performed. 'Non-follow up' status is
determined by the absence of encounter activity to the same DSS ID credit pair as the appointment clinic in the previous 24 months.
NOTE: 'Next Ava. Ind.' Values--'0' = not indicated by the user or calculation to be a 'next available' appointment, '1' = defined
by the user as a 'next available' appointment, '2' = indicated by calculation to be a 'next available' appointment, '3' = indicated
by the user and by calculation to be a 'next available' appointment. 'Wait Time1' = the difference between the 'date desired' and
the date of the appointment. 'Wait Time2' = the difference between the 'date scheduled' and the date of the appointment.
Select PATIENT NAME:
Correct Patient?
No Patient Selected, OK to proceed?
ACT REQ
NOTE: 'APPT TYPE' Values--'0' = user indicated 'Not next available' and calculation indicated 'Not next available' used
'1' = user indicated 'Next available' but calculation indicated next available appt not used
'2' = user indicated 'Not next available' but calculation indicated next available appointment used
'3' = user indicated 'Next available' and calculation indicated 'Next available' apppointment used
WAIT TIME: -------------- the difference between the 'DATE DESIRED' and 'APPT DATE/TIME'
TIME TO APPT.: ----------- days from 'DATE SCHEDULED' to 'APPT DATE/TIME'
APPT STATUS: N - No-show, CC - Canceled by Clinic, NA - No Show & Auto Rebook, CCA -Canceled by Clinic & Auto Rebook,
I - Inpatient, CP - Canceled by Patient, CPA - Canceled by Patient & Auto Rebook, NT - No Action Taken,
F - Future, CI - Checked In, COA - Checked Out/Action Required, CO - Checked Out
No activity found within the parameters specified.
O U T P A T I E N T V I S I T S
Act. Req./not accepted visits
Transmitted, accepted visits
O U T P A T I E N T U N I Q U E S
Act. Req./not accepted unique pts.
Transmitted, accepted unique pts.
<*> OUTPATIENT ENCOUNTER WORKLOAD STATISTICS <*>
For encounter dates
For station:
***NONE ASSIGNED***
Please select fiscal year
XMITED OE MT=U RPT
SCDX MTU
SCDX ASORT
Outpatient Encounters Scanned
Outpatient Encounters Reported
Patient Count
ACRP MT=U STATS
Transmitted Outpatient Encounters with Means Test = 'U'
Medical Ctr
Encounter Date
MT Indicator
* - Transmitted Outpatient Encounter
No 'action required'/not accepted unique patients identified.
'action required'/not accepted unique patient
<*> LIST OF 'ACTION REQUIRED'/NOT ACCEPTED UNIQUE PATIENTS <*>
Would you like to print a detailed list of activity for a division
WARNING: Selection high activity areas will result in lengthy output!
Select type of list
Select transmission status for CHECKED OUT encounters
5:Transmitted, no acknowledgment;6:Transmitted, rejected;7:Transmitted, error;8:Transmitted, accepted
Select Medical Center division for detail:
Required for patient detail!
<*> DETAILED LIST OF DIVISION
Encounters with
Transmission status:
No records found in this category.
uniques identified.
visits identified.
encounters identified.
Outpatient Encounter Workload Statistics
*** Additional Detail Selection ***
Break out workload by clinic group
Specify if subtotals by encounter location CLINIC GROUP should be provided.
List facility 'action required'/not accepted unique patients
Outpatient Encounter Workload
SDZ(
An error has occurred.
CURRENT USER
Scheduling User Data Retrieval
System Default
Setting User Query Default
NULL XMT POINTER
No (Deleted) Outpatient Encounter entry found.
Select Patient name, Clinic name, or Error Code:
Enter as P.patient name, C.clinic name, or E.error name
Searching for patient
Searching for Clinic
Searching for Error Code
Answer with Yes to accept, or No to ignore
Enter P.patient name to select a specific patient,
C.clinic name to select a specific clinic, or E.Error Name
to select a specific error.
If selecting a specific error by its description it may be
necessary to enter more than three characters(Ex. E.Abxxxx).
Because this is a descriptive field, case sensitivity applies.
If just a name is entered, any matches will be displayed in
patient, clinic, error code order. You will have the option
of selecting or ignoring the choice.
Scheduling Option^1N
OPC MENU NOW USED!
OPTIONS MUST BE INDIVIDUALLY CALLED!
Special Survey functionality is obsolete!
SUPERVISOR OPTIONS NO LONGER ACCESSIBLE!
Environmental Checks Started...
Environmental Checks Completed.
Passed
on the 'SDAM APPOINTMENT EVENTS' protocol
is a dangling pointer and must be corrected/removed
before patch SD*5.3*132 can be installed.
Please contact the Customer Support Help Desk for assistance.
-> At least one patch check failed.
-> All patch checks passed.
not Ok
SD*5.3*132 OVERRIDE FLAGS
PACKAGE NAME
NEEDED VERSION
REASON TEXT
REASON NUMBER
Information On Patches Needed For SD*5.3*132 Install
Patch or
...invalid namespace passed!
...override set for '
...override killed for '
Post-Init Started...
Post-Init Finished.
>>> Deleting MAS PARAMETERS (#43) fields...
>>> Deleting HOSPITAL LOCATION (#44) fields...
>>> Deleting APPPOINT STATUS UPDATE LOG (409.65) fields...
>>> Setting 'ACG' cross references...
>>> Queuing task to set 'AG' cross reference.
SDACS CGSCLIST
AG Cross Reference Being Set
-> Option 'SDACS CGSCLIST' has been placed out of service.
Setting 'AG' Cross Reference
>>> Option 'SDACS CGSCLIST' is back in service.
Setting of 'AG' Cross Reference Task Information
>>> Package Override Flag Information
-> Override flag set for '
-> No package override flags set.
-> Fields already deleted.
SD-SITE-PAIT
Unable to update FACILITY NAME field of file 771
Edit entry SD-SITE-PAIT manually
HL7 Parameters Updated Successfully
RE-LINKED
Re-Linked successfully:
Error has occurred.
Please make a note of the following:
Fix -1 Outpatient Encounters
Task queued: #
SDVISIT FIX
COUNT ONLY
Bad encounter entry passed
Unknown Clinic
ERROR OCCURRED
SD TO PCE RESYNC
>>>> Encounter Clean Up Tool for -1 Visit ID's [
DUZ is not defined.
No package with 'SD' namespace exists on the system.
The Unique Visit ID cleanup has run to completion.
End Time:
Run Mode:
Count Only
Fix Entries
>>> Task Stopped by user. <<<
Total number of Outpatient Encounter entries
that will be
Note: Child encounters re-linked as part of parent
re-linking process are not listed below nor
counted in the total above.
Message Format:
Piece Description
1 Status of update
2 Internal Entry Number of Outpatient Encounter file
3 Internal Entry Number of Parent Outpatient Encounter file
4 Internal Entry Number of Visit file
5 Patient Name
6 Encounter Date/Time
7 Hospital Location
Unique Visit ID Cleanup is Complete
SDVISIT MSG
1:Count Only;2:Fix Entries
Select update mode
You are running this routine in scan mode, which will only identify
the problems corrected. Please select a device (queueing allowed) so
that a listing of what would have been done can be obtained.
ACRP cleanup of files 409.73, 409.74, and 409.75
Please enter the date/time that you would like this clean up queued to
run. A summary of what was done will be sent to you and the
recipients of the SCDX AMBCARE TO NPCDB SUMMARY bulletin.
** Unable to schedule correction **
This routine will clean up dangling pointers and orphan entries within
the ACRP transmission files. The following actions/checks will be
(1) Entries in the Transmitted Outpatient Encounter file (409.73)
that do not have a valid pointer to the Outpatient Encounter
file (#409.68) or the Deleted Outpatient Encounter file
(#409.74) are deleted.
(2) Entries in the Transmitted Outpatient Encounter file that have
been rejected by the Austin Automation Center and do not have an
entry in the Transmitted Outpatient Encounter Error file
(#409.75) are marked for re-transmission.
(3) Entries in the Deleted Outpatient Encounter file that do not
have a corresponding entry in the Transmitted Outpatient
Encounter file are deleted.
(4) Entries in the Transmitted Outpatient Encounter Error file that
do not have a valid pointer to the Transmitted Outpatient
Scanning of the Transmitted Outpatient Encounter, Deleted Outpatient
Encounter, and Transmitted Outpatient Encounter Error files for known
problems started on
The following entries in the Transmitted Outpatient Encounter
file (#409.73) will be acted upon when run in fix mode
,0) has bad pointer to Outpatient Encounter file
,0) has bad pointer to Deleted Outpatient Encounter file
,0) rejected with no reason on file (entry in 409.75)
Last entry in Transmitted Outpatient Encounter file checked >>
entries where checked
would have been marked for retransmission
would have been deleted
have bad Outpatient Encounter pointers
have bad Deleted Outpatient Encounter pointers
The following entries in the Deleted Outpatient Encounter
file (#409.74) will be deleted when run in fix mode
,0) not in Transmitted Outpatient Encounter file
Last entry in Deleted Outpatient Encounter file checked >>
entries where checked and
Error file (#409.75) will be deleted when run in fix mode
,0) has bad pointer to Transmitted Outpatient Encounter file
Scan ended on
Use the entry point FIX^SD53105A to run in fix mode
Use the entry point SCAN^SD53105A to re-run in scan mode
SD53105-BULL1
*** Note that process was asked to stop and did not run to completion ***
Process began on
and completed on
entries in the Transmitted Outpatient Encounter file were
checked and
of them were deleted because of bad pointers to the
Outpatient Encounter file and
of them were deleted because of bad
pointers to the Deleted Outpatient Encounter file. In addition to this,
entries were marked for re-transmission because they were rejected and
did not contain a reason for rejection in the Transmitted Outpatient
Encounter Error file.
entries in the Deleted Outpatient Encounter file were
of them were deleted because an associated entry in the
Transmitted Outpatient Encounter file could not be found.
were checked and
Transmitted Outpatient Encounter file.
ACRP - SD*5.3*105
>>> Deleting obsolete triggers on the TRANSMISSION REQUIRED field
(#.04) of the TRANSMITTED OUTPATIENT ENCOUNTER file (#409.73).
Trigger cross reference number
>>> Updating the ERROR CODE DESCRIPTION field (#11) of
the TRANSMITTED OUTPATIENT ENCOUNTER ERROR CODE file
(#409.76) for error codes 420 and 105. Definitions
were modified to reflect receipt of data by NPCD
after close-out.
Date of Encounter is invalid, after date of transmission, or after close-out.
Event Date is missing, invalid, after processing date, or after close-out.
*** The following error occurred while updating descriptions ***
>>> Checking for existance of a valid mail group in the
LATE ACTIVITY MAIL GROUP field (#217) of the MAS
#################### #################### ####################
#################### #################### ####################
#################### #################### ####################
#################### #################### ####################
#################### #################### ####################