| GENERAL DESCRIPTION |
PCE Device Interface module local array structures exported with PCE.
Conventions
An Error Suspension file records data that fails the verification process
or if there are errors in storing.
1. In listings of valid values [1 | 0 | null]
1 denotes TRUE or YES
0 denotes FALSE or NO
null denotes VALUE NOT SUPPLIED BY DATA CAPTURE APPLICATION
2. The PCE Device Interface uses a locally name-spaced array (called
LOCAL in this document ) with the following gross structure to
receive data from an external device. Developers should use an
array in their namespace to represent the LOCAL array. It is
possible that data from multiple providers was captured for the
encounter. The ENCOUNTER node records information about the
"main" provider. It is mandatory that this person be identified
in the ENCOUNTER node. Data will NOT be moved to VISTA if such a
provider is not identified on the ENCOUNTER node. The remaining
nodes in the LOCAL( array [VITALS, DIAGNOSIS, PROCEDURE,
PROBLEM... ] are specific to the particular PROVIDER associated
with the data on that node. If the provider is unknown, (for
example, the identity of the nurse who took the vitals was not
captured on a scanned encounter form) the provider subscript
<PROVIDER IEN> may be set to zero except provider is required for
PROBLEM. This is a concession to reality, and should not be
encouraged. If a provider CAN be identified, they SHOULD be
identified.
Locally name-spaced array:
LOCAL("DIAGNOSIS/PROBLEM",<PROVIDER IEN>)
LOCAL("PROBLEM",<PROVIDER IEN>)
LOCAL("SOURCE")
LOCAL("ENCOUNTER")
LOCAL("DIAGNOSIS",<PROVIDER IEN>)
LOCAL("PROCEDURE",<PROVIDER IEN>)
LOCAL("PROVIDER",<PROVIDER IEN>)
LOCAL("IMMUNIZATION",<PROVIDER IEN>)
LOCAL("SKIN TEST",<PROVIDER IEN>)
LOCAL("EXAM",<PROVIDER IEN>)
LOCAL("PATIENT ED",<PROVIDER IEN>)
LOCAL("HEALTH FACTORS",<PROVIDER IEN>)
LOCAL("VITALS",<PROVIDER IEN>)
Vitals are not processed by PCE but are passed to the
Vitals/Measurement package.
LOCAL("LOCAL",
This data doesn PCE and will not be
processed by PCE, but it may be used to pass local data
to a local process (see protocol for local data
processing).
3. The Encounter and Source nodes are required; the rest are
optional.
4. All entries in the local array are resolved to internal values as
defined below.
5. By convention; use a DUZ = .5 (the POSTMASTER) as a default when
one cannot be determined. This is only for tasked jobs on some
systems.
6. The data in the ENCOUNTER, PROCEDURE, and DIAGNOSIS/ PROBLEM or
DIAGNOSIS nodes are the minimal set for capturing workload
starting 10/1/96. The data in the rest of the nodes with the
associated providers build on the clinically relevant data set
and are not used for workload
7. While ENCOUNTER, PROCEDURE, and DIAGNOSIS/PROBLEM or DIAGNOSIS
values are required to capture workload and generate a bill, they
may not be present in every data set passed through this event
point. For example, data on Vitals may be collected by a Nurse
and passed through the event point for storage independent of
other data associated with the encounter. Because of this, these
are NOT required values in this version.
8. If there is a different (ancillary) hospital location for this
patient encounter, you have to do a separate encounter. Separate
calls for each hospital location are required.
Required Input
LOCAL( LOCAL( is a local array as defined in the remainder
of this document. Developers should use an array in
their namespace to represent the LOCAL array; e.g.,
IBDFPCE.
Result returned
PXCASTAT 1 = event processing occurred and the data was
passed to DHCP.
0 = event processing could not occur. There is data
in LOCAL("ERROR" explaining why.
LOCAL("ERROR" as described below. Denotes Errors. Data associated
with the error was not filed. The node does not
exist if errors do not occur.
LOCAL("ERROR",<NODE>,<PROVIDER
IEN>,<i>,<PIECE>)="Free text message^REJECTED VALUE"
Where <NODE> ::= "ENCOUNTER" | "VITALS" |
"DIAGNOSIS" | "PROCEDURE" |
"PROBLEM" | rest of list|
<PROVIDER IEN> ::= internal entry number of
provider. Is 0 (ZERO) for ENCOUNTER
and SOURCE
<i> ::= sub-entry 'i' for that provider
Is 0 (ZERO) for ENCOUNTER, SOURCE
and PROVIDER
<PIECE> ::= $P( selector in
LOCAL(<NODE>,<PROVIDER IEN>,<i>)
that failed.
The value of <PIECE> may be 0
(ZERO) if a problem is found that
does not relate to a single
specific piece.
LOCAL("WARNING" as described below. Denotes problems with the
data that did not prevent processing. Processing
continued after the warnable condition was detected.
The node does not exist if warning, conditions do
not occur. Warnings do NOT affect the value of
PXCASTAT.
LOCAL("WARNING",<NODE>,<PROVIDER IEN>,<i>,<PIECE>)
="Free text message^QUESTIONABLE VALUE"
Where <NODE> ::= "ENCOUNTER" | "VITALS" |
"DIAGNOSIS" | "PROCEDURE" |
"PROBLEM"
<PROVIDER IEN> ::= internal entry number of
provider. Is 0 (ZERO) for ENCOUNTER
and SOURCE
<i> ::= sub-entry 'i' for that provider
Is 0 (ZERO) for ENCOUNTER, SOURCE,
and PROVIDER
<PIECE> ::= $P( selector in
LOCAL(<NODE>,<PROVIDER IEN>,<i>) in
question.
The value of <PIECE> may be 0
(ZERO) if a problem is found that
does not relate to a single
specific piece.
Entry Point for processing the data in the foreground
FOREGND^PXCA(.LOCAL,.PXCASTAT) All data for the event driver is to
be stored in the local array, LOCAL(, in the
proper format by the source prior to calling
this entry point. This entry point validates and
verifies the data and then if there are no
validation errors, the data is processed in the
foreground. Computation by the source will not
continue until all processing is completed by
any and all 'down-stream' protocol event points.
Entry Point for processing the data in the background on the Host
BACKGND^PXCA(.LOCAL,.PXCASTAT) All data for the event driver is to
be stored in the local array, LOCAL(, in the
proper format by the source prior to calling
this entry point. This entry point validates and
verifies the data and then if there are no
validation errors, the data is processed in the
background via TASKMAN. Computation by the
source may continue.
Entry Point for data validation
VALIDATE^PXCA(.LOCAL) The data in the local array, LOCAL(, is
validated and verified, but is not processed.
Use of this entry point by your application will
result in the data being validated twice, since
it is validated prior to processing by the
FOREGND^PXCAEP and BACKGND^PXCAEP entry points.
If a piece of data cannot be validated, an entry
is placed in the LOCAL("ERROR" node as described
above
Protocol for local data processing
PXCA DATA EVENT Other developers who wish to use any of the data
in the local array, including local additions,
can attach a protocol that calls their routines
to the item multiple of this protocol. This
protocol is activated if there are no errors in
the data validation and after PCE has processed
the data.
For data unique to the encounter
SOURCE data LOCAL("SOURCE") = 1^2^3^4^5, where:
Piece 1
Data Source
Required for PCE
Required for SD
Format: DATA SOURCES file (#839.7)
Piece 2
DUZ
Required for PCE
Required for Scheduling
Piece 3
Form numbers
Not stored by PCE Piece 4
Batch ID
Not stored by PCE Piece 5
Record ID
Not stored by PCE
Encounter data LOCAL("ENCOUNTER") =
1^2^3^4^5^6^7^8^9^10^11^12^13^14^15^16^17^18, where:
LOCAL("ENCOUNTER",modifier[E;1/.01]) = ""
Piece 1
Appointment Date/Time
Required for PCE
Required for Scheduling
Format: Fileman Date/Time
Piece 2
Patient DFN
Required for PCE
Required for Scheduling
Format: Pointer to IHS PATIENT file (#9000001)
Piece 3
Hospital Location IEN
Each hospital location is a separate encounter P,S
Format: Pointer to HOSPITAL LOCATION file (#44)
Piece 4
Provider IEN
This is the person that saw the Patient at the scheduled date and
time.
Required for PCE
Format: Pointer to NEW PERSON file (#200)
Piece 5
Visit CPT code IEN
Format: Pointer to TYPE OF VISIT (#357.69)
Piece 6
SC Condition
Format: [1 | 0 | null]
Piece 7
AO Condition
Format: [1 | 0 | null]
Piece 8
IR Condition
Format: [1 | 0 | null]
Piece 9
EC Condition
Format: [1 | 0 | null]
Piece 10
MST Condition
Format: [1 | 0 | null]
Piece 13
Eligibility Code IEN
Format: Pointer to ELIGIBILITY CODE file (#8)
Piece 14
Check-out date and time
Format: Fileman Date/Time
Piece 15
Provider indicator (relates to 4)
Required for PCE
Format: Set of Codes
P ::= Primary
S ::= Secondary
Piece 16
Attending Physician IEN
(May or may not be the same as 4)
Format: Pointer to NEW PERSON file (#200)
Piece 17
HNC Condition
Format: [ 1 | 0 | null ]
Piece 18
CV Condition
Format: [ 1 | 0 | null ]
All of the remaining entries in the LOCAL( array are specific to a
particular Provider associated with the data on that node. If the
provider is unknown, (for example, the identity of the nurse who
took the vitals isn t recorded on a scanned encounter form), the
provider subscript <PROVIDER IEN> may be set to zero.
Diagnosis and/or Problems, specific to one provider
We recommend that you use these nodes instead of the separate Diagnosis
and Problem nodes.
If no Diagnosis and/or Problems, $D(LOCAL("DIAGNOSIS/PROBLEM")) is true.
LOCAL("DIAGNOSIS/PROBLEM",<PROVIDER IEN>, i) = 1^2^3^4,...17^18 where:
Piece 1
Diagnosis Code IEN
Required for PCE
Required for Scheduling
Format: Pointer to ICD9 DIAGNOSIS file (#80)
Piece 2
Diagnosis Specification Code
Required for PCE
N/A for Problem List
Format: Set of Codes
P ::= Primary
S ::= Secondary
Piece 3
Clinical Lexicon Term IEN
Format: Pointer to EXPRESSIONS file (#757.01)
Piece 4
Problem IEN
Required by Problem List for existing
Format: Pointer to PROBLEM LIST file (#9000011)
Piece 5
Add to Problem List
N/A for PCE
Required by Problem List for new problem
Format: [1 | 0 | null]
Piece 6
Problem Active?
Default is Active if not specified
N/A for PCE
Format: Set of Codes
A ::= Active
I ::= Inactive
Piece 7
Problem Onset Date
N/A for PCE
Format: Fileman Date/Time
Piece 8
Problem Resolved Date
N/A for PCE
Format: Fileman Date/Time
Piece 9
SC Condition
Format: [1 | 0 | null]
Piece 10
AO Condition
Format: [1 | 0 | null]
Piece 11
IR Condition
Format: [1 | 0 | null]
Piece 12
EC Condition
Format: [1 | 0 | null]
Piece 13
Provider Narrative
Required for PCE
Required by Problem List for new problem
Format: free text, 2-80 Characters
Piece 14
Category Header for Provider Narrative
N/A for Problem List
Format: free text, 2-80 Characters
Piece 15
MST Condition
Format: [ 1 | 0 | null ]
Piece 16
HNC Condition
Format: [ 1 | 0 | null ]
Piece 17
CV Condition
Format: [ 1 | 0 | null ]
Piece 18
Order/Resulting
Format: Set of Codes
O ::= Ordering
R ::= Resulting
B ::= Both Ordering and Resulting
LOCAL("DIAGNOSIS/PROBLEM",<PROVIDER IEN>,i,"NOTE") = 1, where:
Piece 1
Provider N/A for PCE
Format: free text, 3-60 Characters
NOTE: If the NOTE node is not needed, it does not have to exist.
NOTE: Information is passed to Problem List if there is data for any of
the positions 5-8 on the "DIAGNOSIS/PROBLEM" node or if there is "NOTE"
node.
NOTE: A provider is required to add a new problem to the Problem List.
Diagnosis data list, specific to one provider, for Problems being treated
at this encounter:
If no Diagnoses, then '$D(LOCAL("DIAGNOSIS",<PROVIDER IEN>))is true.
LOCAL("DIAGNOSIS",<PROVIDER IEN>,i) = 1^2^3^4^...^13^14 where:
Piece 1
Diagnosis code IEN
Required for PCE
Required for Scheduling
Format: Pointer to ICD9 DIAGNOSIS File (#80)
Piece 2
Diagnosis specification code
Will default to "S" if blank
Format: Set of Codes.
P ::= Primary
S ::= Secondary
Piece 3
SC Condition
Format: [1 | 0 | null]
Piece 4
AO Condition
Format: [1 | 0 | null]
Piece 5
IR Condition
Format: [1 | 0 | null]
Piece 6
EC Condition
Format: [1 | 0 | null]
Piece 7
Associated Problem IEN
Format: Pointer to PROBLEM LIST file 9000011
Piece 8
Physician's term for Diagnosis
Required for PCE
Format: free text, 2-80 Characters
Piece 9
Physician's term for Category Header
May have been used as a grouping for a set of related Diagnosis
which the provider selected from
Format: free text, 2-80 Characters
Piece 10
Lexicon IEN
Format: Pointer to EXPRESSIONS File (#757.01)
Piece 11
MST Condition
Format: [ 1 | 0 | null ]
Piece 12
HNC Condition
Format: [ 1 | 0 | null ]
Piece 13
CV Condition
Format: [ 1 | 0 | null ]
Piece 14
Order/Resulting
Format: Set of Codes
O ::= Ordering
R ::= Resulting
B ::= Both Ordering and Resulting
NOTE: PCE recommends using the DIAGNOSIS/PROBLEM node so that the
diagnosis can point to the problem that it relates to.
Procedures data list, specific to one provider
If no Procedures, then '$D(LOCAL("PROCEDURE",<PROVIDER IEN>)) is true.
LOCAL("PROCEDURE",<PROVIDER IEN>,i) = 1^2^3^4^5^6^7^8^9^10^
11^12^13^14,(pieces defined below)
LOCAL("PROCEDURE",<PROVIDER IEN>,i,modifier[E;1/.01]) = ""
Piece 1
CPT4 Procedure code
Required by PCE for V CPT file (Procedures)
if this field is blank then will be stored in V TREATMENT file
Required for Scheduling
Format: Pointer to CPT file (#81)
Piece 2
Quantity Performed
Required for PCE
Required for Scheduling
Format: number > 0
Piece 3
Procedure specification code
For CPT only.
Format: Set of Codes
P ::= Primary
S ::= Secondary
Piece 4
Date/Time Procedure performed
Format: Fileman Date/Time
Piece 5
Primary Associated Diagnosis IEN For this CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 6
Physician's term for Procedure
Required for PCE
Format: free text, 2-80 Characters
Piece 7
Physician's term for Category Header
May have been used as a grouping for a set of related Procedures
which the provider selected from
Format: free text, 2-80 Characters
Piece 8
1st Secondary Associated Diagnosis IEN For this CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 9
2nd Secondary Associated Diagnosis IEN For this CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 10
3rd Secondary Associated Diagnosis IEN For this CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 11
4th Secondary Associated Diagnosis IEN For this CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 12
5th Secondary Associated Diagnosis IEN For this CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 13
6th Secondary Associated Diagnosis IEN For this CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 14
7th Secondary Associated Diagnosis IEN For this CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
NOTE: If a Procedure doesn t have a
CPT code, it can be passed without one and will be stored in the
V Treatment file but will not be used for workload or billing.
Problem data list, specific to one provider
If no Problems, then '$D(LOCAL("PROBLEM",<PROVIDER IEN>)) is true.
LOCAL("PROBLEM",<PROVIDER IEN>,i) = 1^2^3^4^5^...^15 where:
Piece 1
Problem Name
Required for new Problem List, i.e. if Pos. 10 is null
Format: free text
Piece 2
Problem Onset Date
Format: Fileman Date/Time
Piece 3
Problem Active?
Default is ACTIVE if not specified
Format: [1 | 0 | null]
Piece 4
Problem Date Resolved
Format: Fileman Date/Time
Piece 5
SC Condition
Format: [1 | 0 | null]
Piece 6
AO Condition
Format: [1 | 0 | null]
Piece 7
IR Condition
Format: [1 | 0 | null]
Piece 8
EC Condition
Format: [1 | 0 | null]
Piece 9
ICD 9 Code value {optional}
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 10
Problem IEN
Must be null if new problem
Required for editing existing Problem
Format: Pointer to PROBLEM LIST file 9000011
Piece 11
Physician's term for Problem
Null if new problem
Format: free text, 60 Characters Max
Piece 12
Lexicon IEN
Format: Pointer to EXPRESSIONS File (#757.01)
Piece 13
MST Condition
Format: [ 1 | 0 | null ]
Piece 14
HNC Condition
Format: [ 1 | 0 | null ]
Piece 15
CV Condition
Format: [ 1 | 0 | null ]
NOTE: The data in this node is passed to Problem List. A Provider is
required to add a new problem to the Problem List. When a new problem is
added to the Problem List, the problem IEN is not required. If data is
passed to edit existing data, the problem IEN must be passed.
NOTE: It is better to use the DIAGNOSIS/PROBLEM node so that the diagnosis
can point to the problem that it relates to.
Provider data list, specific to one provider
Use this node to pass of additional providers which do not have data
associated with them.
If no additional Providers, then '$D(LOCAL("PROVIDER",< PROVIDER IEN>))
is true.
LOCAL ("PROVIDER",<PROVIDER IEN>= 1^2 where:
Piece 1
Provider indicator
Required for PCE
Format: Set of Codes.
P: = Primary
S: = Secondary
Piece 2
Attending
Format: [1|0| null]
NOTE: If a provider is on the Encounter node and also on this node
then the data on this node will be used for Primary/Secondary indicator.
Immunization data list, specific to one provider
If no immunization entries, then '$D(LOCAL("IMMUNIZATION",<PROVIDER IEN>))
is true.
LOCAL ("IMMUNIZATION",<PROVIDER IEN>,i)=1^2^3^4^5^6^7^8^9^10^11^12^13^14^15
Piece 1
Immunization
Required for PCE
Format: Pointer to IMMUNIZATION File (9999999.14)
Piece 2
Series
Format: Set of Codes.
P::=Partially complete
C::=Complete
B::=Booster
1::=Series1
...
8::=Series8
Piece 4
Reaction
REACTION Field (9000010.11,.06) SET
Format: Set of Codes.
'0' FOR NONE
'1' FOR FEVER;
'2' FOR IRRITABILITY;
'3' FOR LOCAL REACTION OR SWELLING;
'4' FOR VOMITING;
'5' FOR RASH OR ITCHING;
'6' FOR LETHARGY;
'7' FOR CONVULSIONS;
'8' FOR ARTHRITIS OR ARTHRALGIAS;
'9' FOR ANAPHYLAXIS OR COLLAPSE;
'10' FOR RESPIRATORY DISTRESS;
'11' FOR OTHER;
Piece 5
Contraindicated
Format: [1|0|null]
Piece 6
Event D/T
Format: Fileman Date/Time
Piece 7
Remarks
Format: Comment
Piece 8
Primary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80
Piece 9
1st Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 10
2nd Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 11
3rd Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 12
4th Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 13
5th Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 14
6th Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 15
7th Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Skin Test data list, specific to one provider
If no skin test entries, then '$D(LOCAL("SKIN TEST",<PROVIDER IEN>)) is
true. LOCAL ("SKIN TEST",<PROVIDER IEN>,i)=1^2^3^4^5^6^7^8^9^10^11^12^13
Piece 1
SKIN TEST
Required for PCE
Format: Pointer to SKIN TEST File (9999999.28)
Piece 2
READING
Format: Whole number between 0 and 40 inclusive
Piece 3
RESULT
Format: Set of Codes.
P::=Positive
N::=Negative
D::=Doubtful
0::=No Take
Piece 4
Date Read
Format: Fileman Date/Time
Piece 5
Date of Injection
Format: Fileman Date/Time
Piece 6
Primary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80
Piece 7
1st Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 8
2nd Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 9
3rd Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 10
4th Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 11
5th Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 12
6th Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Piece 13
7th Secondary Associated Diagnosis IEN For this mapped CPT only.
Format: Pointer to ICD DIAGNOSIS File (#80)
Examination data list, specific to one provider
If no examination entries, then '$D(LOCAL("EXAM",<PROVIDER IEN>)) is true.
LOCAL ("EXAM",<PROVIDER.IEN>")=1^2
Piece 1
EXAM
Required for PCE
Format: Pointer to EXAM File (9999999.15)
Piece 2
RESULT
Format: Set of Codes.
A::=Abnormal
N::=Normal
Patient Education data list, specific to one provider
If no Patient Education entries, then '$D(LOCAL("PATIENT ED",<PROVIDER
IEN>)) is true. LOCAL ("PATIENT ED",<PROVIDER IEN>,i)=1^2
Piece 1
Topic
Required for PCE
Format: Pointer to EDUCATION TOPICS File (9999999.09)
Piece 2
Level of Understanding
Format: Set of Codes.
1::=Poor
2::=Fair
3::=Good
4::=Group - No Assessment
5::=Refused
Health Factors data list, specific to one provider
If no Health Factors entries, then
'$D(LOCAL("HEALTH FACTORS",<PROVIDER IEN>)) is true. LOCAL ("HEALTH
FACTORS",<PROVIDER IEN>,i)=1^2
Piece 1
Health Factor
Required for PCE
Format: Pointer to HEALTH FACTORS File (9999999.64)
Piece 2
Level/Severity
Format: Set of Codes.
M::=Minimal
MO::=Moderate
H::=Heavy/Severe
Vitals data list, specific to one provider
If no Vitals, then '$D(LOCAL("VITALS",<PROVIDER IEN>)) is true.
LOCAL("VITALS",<PROVIDER IEN>,i) = 1^2^3^4, where:
Piece 1
Type
Required for PCE
Format: Set of Codes.
AG::= ABDOMINAL GIRTH
AUD::= AUDIOMETREY
BP::= BLOOD PRESSURE
FH::= FUNDAL HEIGHT
FT::= FETAL HEART TONES
HC::= HEAD CIRCUMFERENCE
HE::= HEARING
HT::= HEIGHT
PU::= PULSE
RS::= RESPIRATIONS
TMP::=TEMPERATURE
TON::=TONOMETRY
VC::= VISION CORRECTED
VU::= VISION UNCORRECTED
WT::= WEIGHT
Piece 2
Value
Required for PCE
Format: Numeric
Piece 3
Units
Not stored; used for conversions
Format: Set of Codes.
C::=Centigrade (degrees)
CM::=Centimeter
F::= Fahrenheit (degrees)
IN::=Inches
KG::=Kilograms
LB::=Pounds
Piece 4
Date/Time Measurement taken
Format: Fileman Date/Time
If the TYPE is HT: If the UNIT is CM it is converted to IN so that it
can be stored. If the UNIT is "" it is assumed to be
IN. If the TYPE is WT If the UNIT is KG it is
converted to LB so that it
can be stored. If the UNIT is "" it is assumed to be
LB. If the TYPE is TMP If the UNIT is C it is
converted to F so that it can
be stored. If the UNIT is "" it is assumed to be F.
NOTE: This data is passed to the Vitals/Measurement package for validation
and storage.
Local data list, specific to one provider
If no local entries, then '$D(LOCAL("LOCAL",<PROVIDER IEN>)) is true.
LOCAL("LOCAL",<PROVIDER IEN>,i) = Site Specific data encoding
Pieces All
Site Specific data encoding
Not stored in PCE
Format: Site Specific
NOTE: LOCAL("LOCAL" where "LOCAL" is replaced by locally namespaced
string.
|