Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Pointer To FileMan Files |  Fields |  External References |  Global Variables Directly Accessed |  Local Variables  | All
Print Page as PDF
Global: ^ECX(727.816

Package: DSS Extracts

Global: ^ECX(727.816


Information

FileMan FileNo FileMan Filename Package
727.816 CLINIC I EXTRACT DSS Extracts

Description

Directly Accessed By Routines, Total: 2

Package Total Routines
DSS Extracts 2 ECX335PT    ^ECX(727.816    

Pointer To FileMan Files, Total: 4

Package Total FileMan Files
Registration 2 SPECIALTY(#42.4)[10]    PATIENT(#2)[4]    
DSS Extracts 1 DSS EXTRACT LOG(#727)[2]    
Scheduling 1 HOSPITAL LOCATION(#44)[18]    

Fields, Total: 21

Field # Name Loc Type Details
.01 SEQUENCE NUMBER 0;1 NUMBER
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:+X'=X!(X>999999999)!(X<1)!(X?.E1"."1N.N) X S:$D(X) DINUM=X
  • LAST EDITED:  JUL 26, 1999
  • HELP-PROMPT:  Type a Number between 1 and 999999999, 0 Decimal Digits
  • DESCRIPTION:  
    The record number for this extract entry.
  • TECHNICAL DESCR:  
    The internal entry number (IEN) for this record. This entry is DINUMed.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
1 YEAR MONTH 0;2 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>6!($L(X)<6) X
  • LAST EDITED:  MAY 05, 1999
  • HELP-PROMPT:  Answer must be 6 characters in length.
  • DESCRIPTION:  
    A six character string representing the year and the month for which this extract was performed.
  • TECHNICAL DESCR:  
    Format is YYYYMM; Year 2000 compliant.
2 EXTRACT NUMBER 0;3 POINTER TO DSS EXTRACT LOG FILE (#727)
************************REQUIRED FIELD************************
DSS EXTRACT LOG(#727)

  • LAST EDITED:  MAY 11, 1999
  • DESCRIPTION:  
    The corresponding entry in the DSS EXTRACT LOG file (#727) for this extract.
  • TECHNICAL DESCR:  
    A pointer to the DSS EXTRACT LOG file (#727). The primary purpose is to pick up the header for the MailMan transmission message.
  • CROSS-REFERENCE:  727.816^AC^MUMPS
    1)= S ^ECX(727.816,"AC",$E(X,1,30),DA)=""
    2)= K ^ECX(727.816,"AC",$E(X,1,30),DA)
    3)= DO NOT DELETE
    The "AC" cross-reference is essential for managing and purging data in this file.
3 FACILITY 0;4 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>7!($L(X)<1) X
  • LAST EDITED:  MAY 05, 1999
  • HELP-PROMPT:  Answer must be 1-7 characters in length.
  • DESCRIPTION:  
    Identifies the facility for this extract record.
  • TECHNICAL DESCR:  An indicator of the division responsible for the patient encounter. It is a pointer to the MEDICAL CENTER DIVISION file (#40.8).
    For scheduled appointments and appended EKG visits, it is taken from the DIVISION field (3.5) of the HOSPITAL LOCATION file (#44).
    For dispositions, stand-alones, and appended lab and x-ray visits, it is derived from the LOCATION field (#.04)in the OUTPATIENT ENCOUNTER file (#409.68). The LOCATION field points to the HOSPITAL LOCATION file (#44).
    The DIVISION field (#3.5) of the pointed-to file #44 record is used.
    The data is stored as free text.
4 PATIENT NO. - DFN 0;5 POINTER TO PATIENT FILE (#2)
************************REQUIRED FIELD************************
PATIENT(#2)

  • LAST EDITED:  MAY 05, 1999
  • DESCRIPTION:  
    Internal entry number of the PATIENT file (#2) record identifying the patient associated with the clinic visit information.
  • TECHNICAL DESCR:  This field points to a record in the PATIENT file (#2).
    For scheduled appointments and appended EKG visits, it is taken from the PATIENT field (#.01) within the APPOINTMENT field (#1900) multiple of the HOSPITAL LOCATION file (#44).
    For dispositions, stand-alones, and appended lab and x-ray visits, it is taken from the PATIENT field (#.02) in the OUTPATIENT ENCOUNTER file (#409.68).
5 SSN 0;6 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>10!($L(X)<9) X
  • LAST EDITED:  MAY 05, 1999
  • HELP-PROMPT:  Answer must be 9-10 characters in length.
  • DESCRIPTION:  The patient's social security number.
    Any patient with an SSN beginning with "00000" is considered a "test patient" and will not be included in the extract.
  • TECHNICAL DESCR:  Using the patient pointer (DFN) stored in the PATIENT NO. - DFN field (#4) of this extract file (#727.816), SSN data is derived from the SOCIAL SECURITY NUMBER field (#.09) in the PATIENT file (#2).
    "Test" patient status is determined in PAT^ECXUTL3. Any patient with an SSN beginning with "00000" will not be included in the extract.
6 NAME 0;7 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>4!($L(X)<4) X
  • LAST EDITED:  MAY 05, 1999
  • HELP-PROMPT:  Answer must be 4 characters in length.
  • DESCRIPTION:  
    The first four characters of the patient's last name.
  • TECHNICAL DESCR:  Using the patient pointer (DFN) stored in the PATIENT NO. - DFN field (#4) of this extract file (#727.816), NAME data is derived from the NAME field (#.01) in the PATIENT file (#2). The first four characters of the first
    "," piece are used, padded with trailing spaces if necessary.
7 IN OUT PATIENT INDICATOR 0;8 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>1!($L(X)<1) X
  • LAST EDITED:  MAY 05, 1999
  • HELP-PROMPT:  Answer must be 1 character in length.
  • DESCRIPTION:  
    Indicates whether the patient was an inpatient or an outpatient on the date in the DAY field (#8) for this extract record.
  • TECHNICAL DESCR:  This status indicator corresponds to an internal entry number in the LOCATION TYPE file (#40.9), where IEN=1 is the Clinic location, and IEN=3 is the Ward location.
    This field is initialized to a 1, indicating an outpatient status. If a call to IN5^VADPT (using the patient DFN and the event date) returns a patient movement number, then the field is reset to a 3 indicating inpatient
    status.
8 DAY 0;9 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>8!($L(X)<8) X
  • LAST EDITED:  MAY 05, 1999
  • HELP-PROMPT:  Answer must be 8 characters in length.
  • DESCRIPTION:  
    Date in format YYYYMMDD; date with which the clinic visit extract data is associated.
  • TECHNICAL DESCR:  For scheduled appointments and appended EKG visits -- HOSPITAL LOCATION file (#44); APPOINTMENT sub-file (#44.001);
    APPOINTMENT DATE/TIME field (#.01)
    For dispositions, stand-alones, and appended lab and x-ray visits -- OUTPATIENT ENCOUNTER file (#409.68); DATE field (#.01)
    This field is always exactly 8 numeric characters in length. The format is YYYYMMDD; for example, 19970923. If the date cannot be determined, then a default is used. The default date value is the value of the YEAR MONTH
    field (#1) concatenated with "01" for the day (DD) portion.
9 FEEDER KEY 0;10 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>14!($L(X)<14) X
  • LAST EDITED:  MAY 05, 1999
  • HELP-PROMPT:  Answer must be 14 characters in length.
  • DESCRIPTION:  Feeder key is a fixed length field. The ACTION TO SEND field (#5) of the CLINIC AND STOP CODES file (#728.44) for this clinic determines the construction of this key. It is derived from DSS selected stop codes and credit
    stop codes (or MAS selected stop codes and credit stop codes in the absence of DSS selected ones), length of appointment, clinic internal entry number in the CLINICS AND STOP CODES file (#728.44), and whether or not this
    was a no show appointment.
  • TECHNICAL DESCR:  The feeder key is a 14 character code of the form SSSCCCTTTPPPPN; where
    SSS = primary stop code
    CCC = secondary stop code
    TTT = appointment length in minutes
    PPPP = National Clinic code
    N = no-show indicator
    One of three transmission styles may be assigned to the clinic in the CLINICS AND STOP CODES file (#728.44).
    For all styles, SSS and CCC are taken from the CLINICS AND STOP CODES file (#728.44). The DSS STOP CODE field (#3) and DSS CEDIT STOP CODE field (#4) are used for SSS and CCC respectively. If field #3 is null, then the
    STOP CODE field (#1) and CREDIT STOP CODE field (#2) are used. If field #1 is null, then data is taken from the STOP CODE NUMBER field (#8) and the CREDIT STOP CODE field (#2503) of the HOSPITAL LOCATION file (#44). If
    field #8 is null, then both SSS and CCC are set to "000".
    For style 1, CCC is always "000" and PPPP is always "0000".
    Styles 2 and 3, defined in previous versions of DSS Extracts, are no longer valid.
    For style 4, PPPP is the National Clinic code assigned to this clinic; it is taken from the NATIONAL CLINIC filed (#7) of file #728.44. The original source if this data is the NATIONAL CLINIC file (#728,441).
    For style 5, PPPP is always "0000".
    In all styles, N is set to "N" if the STATUS field (#3) in the APPOINMENT sub-file (#2.98) of the PATIENT file (#2) is set to "NO-SHOW".
    In all styles SSS, CCC, TTT and PPPP are padded with leading zeroes as needed; the Feeder is always exactly 14 characters.
10 TREATING SPECIALTY 0;11 POINTER TO SPECIALTY FILE (#42.4) SPECIALTY(#42.4)

  • LAST EDITED:  MAY 06, 1999
  • DESCRIPTION:  
    The treating specialty associated with this extract record, if the patient is an inpatient.
  • TECHNICAL DESCR:  This field is initialized to a null, indicating an outpatient status. If a call to IN5^VADPT (using the patient IEN and the event date) returns a patient movement number (indicating inpatient status), then the value of
    VAIP(8), which is the pointer to the FACILITY TREATING SPECIALTY file (#45.7), is used to get the SPECIALTY field (#1) which points to the SPECIALTY file (#42.4).
11 ENCOUNTER ELIGIBILITY 0;12 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>3!($L(X)<1) X
  • LAST EDITED:  MAY 06, 1999
  • HELP-PROMPT:  Answer must be 1-3 characters in length.
  • DESCRIPTION:  
    The patient's eligibility for this outpatient encounter.
  • TECHNICAL DESCR:  In the OUTPATIENT ENCOUNTER file (#409.68), the ELIGIBILITY OF ENCOUNTER field (#.13) points to the ELIGIBILITY CODE file (#8).
    Then the MAS ELIGIBILITY CODE field (#8) of file #8 points to the MAS ELIGIBILITY CODE file (#8.1).
    The pointer value to file #8.1 is converted by ELIG^ECXUTL3 to the corresponding eligibility code used by NPCD. This code is composed of two or three numeric characters.
12 PRIMARY CARE PROVIDER 0;13 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>11!($L(X)<2) X
  • LAST EDITED:  MAY 10, 1999
  • HELP-PROMPT:  Answer must be 2-11 characters in length.
  • DESCRIPTION:  
    The Primary Care Provider assigned to this patient.
  • TECHNICAL DESCR:  For scheduled appointments and appended EKG visits, use the APPOINTMENT DATE/TIME field (#.01) in the APPOINTMENT field (#1900) multiple of the HOSPITAL LOCATION file (#44).
    For dispositions, stand-alones, and appended lab and x-ray visits, use the DATE field (#.01) in the OUTPATIENT ENCOUNTER file (#409.68).
    The date along with the patient pointer (DFN) stored in the PATIENT NO. - DFN field (4) of the extract record is used to make a call to the Scheduling API, OUTPTPR^SDUTL3. The pointer (IEN) to the NEW PERSON file (#200),
    retuned by the API, is used.
    A "2" is prefixed to the pointer value to indicate that the source file is "200", and the data is stored as free text.
13 PC PROVIDER PERSON CLASS 0;14 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>7!($L(X)<7) X
  • LAST EDITED:  MAY 10, 1999
  • HELP-PROMPT:  Answer must be 7 characters in length.
  • DESCRIPTION:  The field will hold the VA Code associated with the active Person Class of the Primary Care Provider as assigned by through the PCMM application. The VA Code is always of the form "V"_six numeric digits; exactly 7
    characters in length.
  • TECHNICAL DESCR:  NEW PERSON file #200, Field #5; file #8932.1. Active Person Class is determined by $$GET^XUA4A71(PERS,DATE), where PERS is the IEN from file #200.
14 PC PROVIDER NPI 0;15 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>8!($L(X)<1) X
  • LAST EDITED:  MAY 10, 1999
  • HELP-PROMPT:  Answer must be 1-8 characters in length.
  • DESCRIPTION:  
    The Primary Care Provider's National Provider Identifier code.
  • TECHNICAL DESCR:  When National Provider Identifier (NPI) codes become available, this field will hold the Primary Care Providerovider NPI.
    Field will be set to null until data becomes available.
15 ASSOCIATE PC PROVIDER 0;16 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>11!($L(X)<2) X
  • LAST EDITED:  MAY 06, 1999
  • HELP-PROMPT:  Answer must be 2-11 characters in length.
  • DESCRIPTION:  
    This is a reference to the NEW PERSON file (#200) for the provider who is the patients Associate Provider for Primary Care as assigned with the PCMM application. The IEN to file #200 is prefixed with the character 2.
  • TECHNICAL DESCR:  
    This data element will be obtained by use of a function provided by the PCMM application.
16 ASSOC. PC PROV. PERSON CLASS 0;17 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>7!($L(X)<7) X
  • LAST EDITED:  MAY 06, 1999
  • HELP-PROMPT:  Answer must be 7 characters in length.
  • DESCRIPTION:  The field will hold the VA Code associated with the active Person Class of the Associate Primary Care Provider as assigned by through the PCMM appilcation. The VA Code is always of the form "V"_six numeric digits;
    exactly 7 characters in length.
  • TECHNICAL DESCR:  
    NEW PERSON file #200, Field #5; file #8932.1. Active Person Class is determined by $$GET^XUA4A71(PERS,DATE), where PERS is the IEN from file #200.
17 ASSOCIATE PC PROVIDER NPI 0;18 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>8!($L(X)<1) X
  • LAST EDITED:  MAY 07, 1999
  • HELP-PROMPT:  Answer must be 1-8 characters in length.
  • DESCRIPTION:  
    The Associate Primary Care Provider's National Provider Identifier.
  • TECHNICAL DESCR:  
    When National Provider Identifier (NPI) codes become available, this field will hold the Associate Primary Care Provider NPI.
18 CLINIC 0;19 POINTER TO HOSPITAL LOCATION FILE (#44) HOSPITAL LOCATION(#44)

  • LAST EDITED:  MAY 07, 1999
  • DESCRIPTION:  
    Reference to the Clinic (if any) associated with the patient encounter.
  • TECHNICAL DESCR:  
    Internal entry number of the Clinic from the HOSPITAL LOCATION file (#44).
19 CPT CODES & MODIFIERS 1;1 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>120!($L(X)<120) X
  • OUTPUT TRANSFORM:  S Y=$$CPTOUT^ECXUTL3(Y)
  • LAST EDITED:  JUN 14, 1999
  • HELP-PROMPT:  Answer must be 120 characters in length.
  • DESCRIPTION:  The primary CPT code and modifier(s) followed by secondary CPT code(s) and modifier(s) in a concatenated string. Only the first CPT code is required. Each CPT code is exactly 5 characters and each modifier is exactly 2
    characters. Each CPT code plus modifier(s) string is exactly 15 characters in length. If there are fewer than 5 modifiers, then the segment must be padded to the right with space characters.
    There may be fewer than 8 CPT codes for a visit record, but the total length of field #18 is always 120 characters, many of which may be space characters (i.e., ASCII code 32).
  • TECHNICAL DESCR:  Using the internal entry number for the encounter in the OUTPATIENT ENCOUNTER file (#409.68), the VISIT FILE ENTRY field (#.05) is determined. This entry is used to make a call to the Patient Care Encounter API,
    ENCEVENT^PXAPI. The API returns all visit data in the ^TMP("PXKENC",$J) array.
    If a Primary Provider is specified for this patient visit, then the first CPT code associated with that Primary Provider is used as the primary CPT code. Otherwise, the first CPT code listed in the array is used as the
    primary CPT code. The remaining CPT codes are used as secondary CPT codes, upto a total of 7 secondary CPT codes.
    Modifiers are found in the CPT MODIFIERS file (#81.3), but it is not known at this time how modifiers will be stored in the Visit file structure.
20 PRIMARY CARE TEAM 1;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>4!($L(X)<1) X
  • LAST EDITED:  MAY 10, 1999
  • HELP-PROMPT:  Answer must be 1-4 characters in length.
  • DESCRIPTION:  
    The primary care team assigned to this patient.
  • TECHNICAL DESCR:  For scheduled appointments and appended EKG visits, use the APPOINTMENT DATE/TIME field (#.01) in the APPOINTMENT field (#1900) multiple of the HOSPITAL LOCATION file (#44).
    For dispositions, stand-alones, and appended lab and x-ray visits, use the DATE field (#.01) in the OUTPATIENT ENCOUNTER file (#409.68).
    The date along with the patient pointer (DFN) stored in the PATIENT NO. - DFN field (#4) of the extract record is used to make a call to the Scheduling API, OUTPTTM^SDUTL3. The pointer (IEN) to the TEAM file (#404.51),
    retuned by the API, is used. The data is stored as free text.

External References

Name Field # of Occurrence
$$CPTOUT^ECXUTL3 19OT+1

Global Variables Directly Accessed

Name Line Occurrences  (* Changed,  ! Killed)
^ECX(727.816 - [#727.816] 2(XREF 1S), 2(XREF 1K)

Local Variables

Legend:

>> Not killed explicitly
* Changed
! Killed
~ Newed

Name Field # of Occurrence
>> DA 2(XREF 1S), 2(XREF 1K)
>> DINUM .01+1*
X .01+1!, 1+1!, 2(XREF 1S), 2(XREF 1K), 3+1!, 5+1!, 6+1!, 7+1!, 8+1!, 9+1!
, 11+1!, 12+1!, 13+1!, 14+1!, 15+1!, 16+1!, 17+1!, 19+1!, 20+1!
>> Y 19OT+1*
>> Y(0 19OT+1*
Info |  Desc |  Directly Accessed By Routines |  Pointer To FileMan Files |  Fields |  External References |  Global Variables Directly Accessed |  Local Variables  | All