308 lines
10 KiB
Plaintext
308 lines
10 KiB
Plaintext
English French Notes Complete/Exclude
|
|
HBPC Patient Visit Data Report
|
|
(continued from previous page...)
|
|
Visit Data
|
|
Visit Date:
|
|
Prov No.:
|
|
Prov Name:
|
|
CPT Code:
|
|
HBPC Visit Data Date Range Report
|
|
Visit Data by Date Range
|
|
All Providers Visit
|
|
Last 4:
|
|
Diagnosis:
|
|
HBPC Patient Discharge Data Report
|
|
Patient Discharge Data
|
|
20. Primary Diagnosis @ D/C:
|
|
2. Discharge Date:
|
|
21. Secondary Diagnoses @ D/C:
|
|
4. Marital Status @ Discharge:
|
|
Hearing @ Discharge:
|
|
5. Living Arrangements @ D/C:
|
|
23. Expressive Communication @ D/C:
|
|
6. Discharge Status:
|
|
24. Receptive Communication @ D/C:
|
|
7. Transfer Destination:
|
|
8. Type of Destination Agency:
|
|
Dressing @ Discharge:
|
|
9. Cause of Death:
|
|
Toilet Usage @ Discharge:
|
|
Transferring @ Discharge:
|
|
Eating @ Discharge:
|
|
Walking @ Discharge:
|
|
26. Bowel Continence @ Discharge:
|
|
Bladder Continence @ Discharge:
|
|
28. Adaptive Tasks @ Discharge:
|
|
29. Behavior Problems @ Discharge:
|
|
31. Mood Disturbance @ Discharge:
|
|
32. Caregiver Limitations @ D/C:
|
|
33. Person Completing Discharge:
|
|
Date Discharge Completed:
|
|
case manager
|
|
case managers
|
|
Case Manager
|
|
Select Admissions or Discharges
|
|
Enter 'A' to include Admissions on the report, 'D' to choose Discharges.
|
|
HBPC
|
|
Date Range Report
|
|
by Date Range
|
|
found for Date Range selected.
|
|
HBPC Provider File Report
|
|
Provider File
|
|
Grade
|
|
Provider Name
|
|
Degree
|
|
HBHC Team
|
|
Prov #
|
|
be transmitted.
|
|
No data on file to transmit.
|
|
This option re-transmits the same data included in the last file created for
|
|
transmission to Austin. It should only be run under special circumstances and
|
|
should be coordinated with Austin. Do you wish to continue
|
|
A 'Yes' response will re-transmit the file to Austin. A 'No' response will
|
|
return to the menu without any data being transmitted.
|
|
Re-transmission request has been queued.
|
|
HBPC Re-Transmit
|
|
HBHC Site:
|
|
XXX@Q-HBH.VA.GOV
|
|
This patient has no records containing errors on file.
|
|
Evalution/Admission
|
|
Another user is editing this
|
|
1 for Admit
|
|
2 for Reject
|
|
This record contains
|
|
data. Are you sure you want
|
|
Admit/Reject Action field ('Yes' will delete the
|
|
Admit/Reject Action field must either contain
|
|
or the
|
|
data MUST be deleted by responding 'Yes'.
|
|
1 or 2 for Transfer
|
|
4 for Died on HBHC
|
|
3, 5 or 9 for Discharge
|
|
Discharge Status field ('Yes' will delete the
|
|
Discharge Status field must contain
|
|
Beginning Report Date:
|
|
Ending Report Date:
|
|
Ending Report Date must be closer to today than the Beginning Report Date
|
|
HBPC Team:
|
|
==== End of Report ====
|
|
Transmit Status Flag must be reset before editing this record is allowed.
|
|
Due to automatic Form 6 Correction Record generation, Transmit Status Flag
|
|
CANNOT be reset without this information. Contact IRM to enter this
|
|
information using FileMan.
|
|
Do you wish to reset the Flag
|
|
A 'Yes' response will reset the Transmit Status Flag field data. A 'No'
|
|
response will return you to the menu without resetting the Transmit
|
|
Status Flag.
|
|
BIRTH YEAR:
|
|
SEX:
|
|
Male (1)
|
|
Female (2)
|
|
RACE:
|
|
Black (2)
|
|
American Indian/Alaskan Native (4)
|
|
White (1)
|
|
Hispanic Origin (3)
|
|
Asian/Pacific Islander (5)
|
|
Not Determined (9)
|
|
RACE: Obsolete Field Jan 2003
|
|
*** Contact MAS if value is incorrect. ***
|
|
Do you wish to include ALL
|
|
on the report
|
|
A 'Yes' response will include ALL
|
|
. A 'No' response will
|
|
prompt for an individual
|
|
Select HBPC
|
|
Census Report
|
|
Case Census
|
|
Street Address
|
|
City
|
|
No data found for
|
|
by Date Range selected.
|
|
Patient visit records with pseudo social security numbers (SSNs) exist.
|
|
Print the 'Pseudo Social Security Number Report' located on the HBHC Reports
|
|
Menu to obtain a list of patients with invalid SSNs. HBHC must determine
|
|
what corrective action is appropriate to eliminate these records from the
|
|
HBHC Information System.
|
|
Note: Please use Appointment Management to Correct Visit Errors. Run
|
|
Edit Form Errors Data option when corrections are complete.
|
|
CPT Code must contain 5 numerics for use in a range.
|
|
Will CPT Codes selected be a Range of codes (Y/N)
|
|
Enter 'Y' for Yes, a range of CPT Codes is requested, 'N' for No, individual CPT codes will be selected.
|
|
Select Beginning CPT Code:
|
|
Select Ending CPT Code:
|
|
Ending CPT Code in range must be greater than the Beginning CPT Code
|
|
(filed for transmit) in ^HBHC(631)
|
|
Processing Admission/Form 3 Data
|
|
Processing Correction/Form 6 Data
|
|
Processing Discharge/Form 5 Data
|
|
Data on file has been transmitted to Austin; duplicate transmission not allowed.
|
|
Transmit Report will be printed on device:
|
|
HBPC Transmission
|
|
Transmission request has been queued. Task number:
|
|
Processing Visit/Form 4 Data
|
|
Beginning Post-Initialization Process
|
|
, Admission Date (#17) field, cross-reference, in HBHC
|
|
Patient (#631) file, to clean up possible dangling cross-reference.
|
|
reindexing complete.
|
|
- Locating patient records in HBHC Patient (#631) & HBHC Visit (#632) files
|
|
that have a pseudo social security number (SSN). These are invalid for HBHC
|
|
purposes. This routine also locates & deletes any records in the HBHC
|
|
Transmit (#634) file containing pseudo SSNs. Two reports of Patient Names are
|
|
printed listing those patients that must be resolved. See Patch Narrative
|
|
for detailed resolution instructions.
|
|
Please select a PRINTER for device. HBHC will need these Pseudo SSN Reports
|
|
to resolve the invalid SSNs.
|
|
HBHC Pseudo SSN Report
|
|
No patients found with pseudo SSNs. No resolution required!!
|
|
Pseudo SSN Patch Related
|
|
Invalid Message Type
|
|
Invalid Header Segment
|
|
Invalid Receiving Application
|
|
Receiving Application is Inactive
|
|
Invalid Sending Application
|
|
Invalid Sending Facility
|
|
Invalid Receiving Facility
|
|
Invalid HL7 Version
|
|
Invalid HL7 version for Receiving Application
|
|
Inappropriate HL7 Processing ID
|
|
Invalid Message Type for Receiving Application
|
|
No Signature Code on File
|
|
Invalid Electronic Signature Code
|
|
FHS,BHS,MSH,MSA
|
|
FHS,BHS,MSH
|
|
FHS,BHS
|
|
SKIP_EVENT
|
|
at SENDACK^HLCS entry point
|
|
Entry in HL COMMUNICATION SERVER PARAMETER file (#869.3) has
|
|
not been made. Entry must be made in order to start execute
|
|
this option.
|
|
Default number of incoming servers has not been entered into
|
|
the HL COMMUNICATION SERVER PARAMETER file (#869.3). Will use
|
|
a value of
|
|
Default number of incoming servers is set to
|
|
incoming servers are currently running. No more
|
|
incoming servers will be started.
|
|
Default number of outgoing servers has not been entered into
|
|
Default number of outgoing servers is set to
|
|
outgoing servers are currently running. No more
|
|
outgoing servers will be started.
|
|
Incoming filer queued as task number
|
|
Unable to queue incoming filer
|
|
Outgoing filer queued as task number
|
|
Unable to queue outgoing filer
|
|
No incoming filers are running
|
|
has been asked to stop
|
|
No outgoing filers are running
|
|
Are you sure you want to stop all incoming filers ?
|
|
Stopping all incoming filers will prevent messages being
|
|
received through Logical Links from being passed to the
|
|
appropriate application. Answer 'YES' if you really want
|
|
this to occur.
|
|
Incoming filers will not be stopped
|
|
Please wait while all incoming filers are asked to stop ...
|
|
All incoming filers have been asked to stop
|
|
Are you sure you want to stop all outgoing filers ?
|
|
Stopping all outgoing filers will prevent messages from
|
|
being transmitted to external systems through Logical
|
|
Links. Answer 'YES' if you really want this to occur.
|
|
Outgoing filers will not be stopped
|
|
Please wait while all outgoing filers are asked to stop ...
|
|
All outgoing filers have been asked to stop
|
|
HL7 Incoming Filer
|
|
HL7 Outgoing Filer
|
|
Unable to create/find entry in HL COMMUNICATION SERVER
|
|
PARAMETER file (#869.3). Entry must exist in order for
|
|
the incoming & outgoing filers to run. Use FileMan to
|
|
create an initial entry for editing.
|
|
Initial entry in HL COMMUNICATION SERVER PARAMETER file
|
|
(#869.3) has been created.
|
|
11Default number of incoming filers;12Default number of outgoing filers
|
|
Okay to shut down all Links and Filers
|
|
Shutdown Aborted!
|
|
Shutting down all Links and Filers...
|
|
Shutdown and restart ALL AUTOSTART links and filers. Okay
|
|
RESTART Aborted!
|
|
Restarting all Autostart-Enabled Links and Filers...
|
|
HLJ(870,
|
|
Halting
|
|
Shutdown
|
|
Enabled
|
|
Low Level Protocol
|
|
ERROR
|
|
Make Connection
|
|
-1^Inital Connection Failed
|
|
Got Connection
|
|
HELO
|
|
-1^Initial HELO Failed
|
|
Send Data
|
|
-1^No 220 after send
|
|
TURN
|
|
-1^No 220 after Turn
|
|
-1^No DATA cmd
|
|
QUIT
|
|
HCS-HOME
|
|
-1^Missing input paramerter
|
|
-1^Bad Logical Link
|
|
Client Setup
|
|
500 Bad CMD:
|
|
Ready for
|
|
Get Data
|
|
PARAM
|
|
Data Sent
|
|
Cmd Read
|
|
Cmd Send
|
|
Server Setup
|
|
DECODE
|
|
500 Data error
|
|
HLJ(773,
|
|
HLJ(772,
|
|
DATA PARAM=
|
|
PARAM=
|
|
1 Out of sync:
|
|
Disconnect
|
|
Logging IO to ^XTMP('HL',N
|
|
Slave Check
|
|
Master Check
|
|
Slave Request
|
|
Slave Ack0
|
|
Slave Read Data
|
|
Slave Write NAK
|
|
SEND NAK
|
|
Master Check Queue
|
|
*Out Queue Empty
|
|
Master Bid
|
|
Master Bid Wait Ack0
|
|
WAIT ACK
|
|
Master Write
|
|
WRITE:
|
|
Write:
|
|
Master Wait for Ack
|
|
WAITING ACK
|
|
HL7 Debug Log
|
|
READ:
|
|
FINISHED READ FOR DLE:
|
|
FINISHED READ FOR ENQ:
|
|
Type Q to Quit:
|
|
In State :
|
|
data set hang-up
|
|
INCOMING MESSAGE
|
|
READ ACK
|
|
VALIDATE NACK
|
|
LLP-NACK
|
|
HLTRANS=
|
|
HLC1=
|
|
HLBLOCK=
|
|
HLC2=
|
|
HLXOR=
|
|
communication server-wide
|
|
in queue
|
|
LLP-ACK
|
|
input queue
|
|
IN STATE
|
|
#################### #################### ####################
|
|
#################### #################### ####################
|
|
#################### #################### ####################
|
|
#################### #################### ####################
|
|
#################### #################### ####################
|