DBIA-5624    ICR (5624)

The accession area of the Lab.

This represents the functional area of the Lab. Must be
chosen from a set of codes.

If another accession area is designated here, that other
accession area will be used to find the next "available" accession number
which will be updated on the other accession area.

Abbreviation for the accession area.  Must have
programmer privileges to alter this entry.

This field will be used to determine which lab division a
particular accession area belongs.  If this field is not filled in, CP
(Clinical Pathology ) will be assumed.

TECHNICAL DESCR:    There can only be two possible laboratory divisions.
Anatomical Pathology or Clinical Pathology.  This field is used to group
workload reports and data.

Mumps code that is triggered by the Accession Transform
field.

NOTES: TRIGGERED by the ACCESSION TRANSFORM field of the ACCESSION File.

This field is used to build the unique accession
identifier number.  It is used as the first two characters of the number.  Use
the numbers 1-9 and uppercase letters A-Z to designate the identifier. For
example, if you enter 99 all accession identifiers for this accession area
will start with 99, e.g. 9923400025.

If a single character is used the system will append a leading zero to the
unique identifier generated.

No two accession areas can use the same identifier.

Changing the identifier should only be performed when accessioning is not
occurring and when a situation requires it since personnel will memorize this
identifier as representing the accesson area.

Do NOT switch identifiers between active accession areas since this could
compromise the uniqueness of the resulting unique identifier (UID). The
software when generating a UID checks for the existence of the UID it will
create for an accession. If it currently exists the UID being created will
have "00" as the numeric identifier.

The date of the accession.

The date of the accession.

The numeric part of the accession.

The internal pointer to file 63 is stored here.

The pointer to the File of Files for the entity in field
.01 is stored here.

The date part of the original accession is stored here.

The date the order was placed is stored here.

The internal specimen number is stored here.

The identity from e.g. reference labs etc. is stored
here.

The service/location from which the original order came.
The report is routed back to this location.

The internal number of the provider requesting the
test(s) is stored here.

The treating specialty of the location requesting the
test.

TECHNICAL DESCR: This node may be set from the default treating specialty
field (#607) of the LABORATORY SITE file (#69.9). The 19th. peice of LRPARAM
variable.

The pointer to the person (NEW PERSON file) creating this
accession is stored here.

This field holds the type of hospital location.
$P(^SC(X,0),U,3) It is used primarily for WKLD calculations. Since the patient
may be discharged or admitted before the WKLD calculation routines run.  This
field holds a permanent location type.

This field contains the location placing the order for
this patient.

The original order number is stored here.

The printable form of the Accession is stored here.

This is the UID used by the HOST LEDI system for this
order/accession.  This field is used by the LEDI software.

This field contains the pointer to the INSTITUTION file
for the MailMan domain location of the computer system. All LEDI results are
returned to the Ordering computer system.

Location to send LEDI HL7 result messages. This field is used by LEDI
software.

This field contain the pointer to the INSTITUTION file
for the actual collection site. The ordering site is the MailMan location of
the computer system. MailMan domain location and the collecting site may be
different.  This field is used by LEDI software.

Each Order/Accession is given a HOST UID. The UID is
stored in this location. If LEDI software is used to accession specimens,
usually the collecting sites UID is used to track specimens. If the collecting
UID conflict is the HOST system number sequence, the HOST UID will be used
instead of the collecting site's UID. This field is used by LEDI software.

This field contains the collecting sites UID for this
specimen. This field is used by LEDI software.

This field contains the division of the person ordering
the test for this accession number. The DUZ(2) is used to determine the
division pointer. In some cases this field may be blank, example auto
accession controls.

The date/time the specimen was taken.

The date/time the specimen arrived at the lab.

The date/time all results for the accession are
available.

9999999 minus the internal entry in field 9 .

The pointers to the Laboratory Tests for this accession.

The pointers to the Laboratory Tests for this accession.

The DUZ of the person verifying the test.  NOTE: This
field previously contained technologist initials.  Converted with the release
of version 5.2.

If null, the test is incomplete.  Otherwise, it is the
date/time of completion.

The site/specimen from the Topography Field file.  There
may be more than one specimen for certain types of accessions.

The site/specimen from the Topography field file.  There
may be more than one specimen for certain types of accessions

The collection sample is from file 62.