PXK VISIT DATA EVENT    ICR (1298)

The Scheduling Developers are requesting permission to
hook the protocol named SDAM PCE EVENT to the ITEM multiple of the protocol
named PXK VISIT DATA EVENT.

This protocol event point was developed to publish data collected by PCE
during an encounter via manual data entry or scanned encounter forms.  The
data represents elements that are stored in the Visit file (9000010) and other
PCE V-Files.

The data is stored in a ^TMP global array with subscripts denoting the
category of published data.  An AFTER and BEFORE subscript are included to
distinguish changes made to data elements during the encounter session.  The
data published in the ^TMP global represents data from one encounter.  The
structure of the ^TMP global that is published is:

^TMP("PXKCO",$J,VISIT,"V FILE STRING",V FILE RECORD,DD SUBSCRIPT,
"AFTER/BEFORE")=DATA

In cases where there is a CPT modifier, the following structure will be used,
this will capture multiple entries for the sub-file.
^TMP("PXKCO",$J,VISIT,"V FILE STRING",V FILE RECORD,DD SUBSCRIPT,
"AFTER/BEFORE",DATA)=""

In cases where there is an Immunization VIS, Other Diagnosis, or Remarks, the
following structure will be used, this will capture multiple entries for the
sub-file.
^TMP("PXKCO",$J,VISIT,"V FILE STRING",V FILE RECORD,DD SUBSCRIPT,
"AFTER/BEFORE",V SUBFILE RECORD)=DATA

Temporary global file root:  ^TMP

Subscript Piece:  1 Description:  String notation representing Package
Contents:  "PXKCO"

Subscript Piece:  2 Description:  Job Number Contents:  $J

Subscript Piece:  3 Description:  Internal Entry Number of the Visit (IEN)
Contents:  Number

Subscript Piece:  4 Description:  String representing the Visit or V file data
category.  The
"SOR" string refers to the PCE Data Source file (839.7) which is not a
V-File.  Contents:
"CPT"  = V CPT (procedure)
9000010.18
"HF"   = V Health Factors
9000010.23
"ICR"  = V Imm Contra/Refusal Events
9000010.707
"IMM"  = V Immunization
9000010.11
"PED"  = V Patient Ed
9000010.16
"POV"   = V POV (diagnosis)
9000010.07
"PRV"  = V Provider
9000010.06
"SK"   = V Skin Test
9000010.12
"SOR"  = PCE Data Source
839.7
"TRT"  = V Treatment
9000010.15
"VST"  = Visit file
9000010
"XAM"  = V Exam
9000010.13
"CSTP"  = Visit file
9000010

This subscript contains child visits used to store additional Stop
Codes.

Subscript Piece:  5 Description:  Internal entry number of the entry in the
file represented
in subscript #4 Contents:  Number

Subscript Piece:  6 Description:  Subscript or DD node on which the data is
stored.  Every DD
node is published whether or not there is any data for that node.  The
exception to this is when an entry is deleted from the file, only the 0
node is posted.

"ELAP" is the exception.  There is no DD subscript in the Visit file
that corresponds to this string.  "ELAP" represents the patient's
eligibility and appointment type for the encounter and has the following
structure: ^TMP("PXKCO",$J,VISIT,"VST",VISIT,"ELAP","BEFORE") or
^TMP("PXKCO",$J,VISIT,"VST",VISIT,"ELAP","AFTER") Contents:  0 800 811 or
"ELAP"

Subscript Piece:  7 Description:  String designating whether or not the data
is an "AFTER" or
"BEFORE" reflection of the data.

* If all the "BEFORE"s are blank, then the data represents a new entry.
* If a node was edited, the "BEFORE" is the value before it was edited,
and the "AFTER" is the value after is was edited.
* If the file entry was deleted, only the 0 node is returned; the
"AFTER" is blank, and the "BEFORE" is the 0 node as it appeared before
it was deleted. Contents:  "AFTER" "BEFORE"

Subscript Piece:  8 Description: For Immunizations that contain VIS, Other
Diagnosis, or
Remarks, this subscript will contain the Internal Entry Number (IEN) of
the multiple for this sub-file entry.



DATA:

The DATA that exists to the right of the global node is a reflection of data
as it appears in the global node of the IEN of the file (noted in subscript
#5) and the NODE of that IEN (described in subscript #6).  Refer to the Data
Dictionary for the Visit and V-Files for the format of the data.

The data stored on the "ELAP" node is the only exception to this.  "ELAP" does
not represent a Data Dictionary node and does not have a corresponding DD
definition.  The data stored on this node has the following structure:

ELIG PTR^ELIG TEXT^APPT PTR^APPT TEXT