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 |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries |  External References |  Global Variables Directly Accessed |  Local Variables |  All
Print Page as PDF
Global: ^MDC(704.002

Package: Clinical Procedures

Global: ^MDC(704.002


Information

FileMan FileNo FileMan Filename Package
704.002 CP_HL7_LOG Clinical Procedures

Description

Directly Accessed By Routines, Total: 6

Package Total Routines
Clinical Procedures 6 MDPRE16    ^MDC(704.002    MDCPHL7A    MDCPHL7B    MDCPSIGN    MDCPURG    

Accessed By FileMan Db Calls, Total: 3

Package Total Routines
Clinical Procedures 3 MDCLIO1    MDCPHL7B    MDPRE16    

Pointed To By FileMan Files, Total: 1

Package Total FileMan Files
Clinical Procedures 1 CP_HL7_LOG_REASON(#704.004)[.01]    

Pointer To FileMan Files, Total: 4

Package Total FileMan Files
Health Level Seven 2 HL7 MESSAGE TEXT(#772)[.05]    HL7 MESSAGE ADMINISTRATION(#773)[.04]    
Clinical Procedures 1 CP TRANSACTION(#702)[.07]    
Registration 1 PATIENT(#2)[.06]    

Fields, Total: 12

Field # Name Loc Type Details
.01 MESSAGE_ID 0;1 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>38!($L(X)<38)!'(X'?1P.E) X
  • LAST EDITED:  MAR 19, 2009
  • HELP-PROMPT:  Answer must be 38 characters in length
  • DESCRIPTION:  This field identifies the Clinical Flowsheets HL7 message. This MESSAGE_ID is generated by the Clinical Flowsheets system.
    An example MESSAGE ID is : {99C25CEA-B3AD-C4B4-4A7F-38CC9BF94514}
  • FIELD INDEX:  PK (#908) REGULAR IR LOOKUP & SORTING
    Unique for:  Key A (#85), File #704.002
    Short Descr:  Uniqueness Index for Key 'A' of File #704.002
    Description:  This cross-reference defines the primary key for the CP_HL7_LOG file.  It references the .01 field, which contains a GUID.
    Set Logic:  S ^MDC(704.002,"PK",$E(X,1,38),DA)=""
    Kill Logic:  K ^MDC(704.002,"PK",$E(X,1,38),DA)
    Whole Kill:  K ^MDC(704.002,"PK")
    X(1):  MESSAGE_ID  (704.002,.01)  (Subscr 1)  (Len 38)
.02 STATUS 0;2 SET
  • '1' FOR ENTERED;
  • '2' FOR AWAITING PROCESSING;
  • '3' FOR ERROR;
  • '4' FOR PROCESSED;

  • LAST EDITED:  MAR 24, 2009
  • HELP-PROMPT:  Select the status of this HL7 message.
  • DESCRIPTION:  
    This field indicates the status of this Clinical Flowsheets HL7 message (MESSAGE_ID field(#.01)).  This status is maintained by Clinical Flowsheets and HL7 message processing.
  • FIELD INDEX:  AS (#907) REGULAR IR SORTING ONLY
    Short Descr:  Sort on status
    Description:  This cross reference allows an easy sort by status, thus allowing a query that searches, for example, for all messages in "AWAITING_PROCESSING" status.
    Set Logic:  S ^MDC(704.002,"AS",$E(X,1,30),DA)=""
    Kill Logic:  K ^MDC(704.002,"AS",$E(X,1,30),DA)
    Whole Kill:  K ^MDC(704.002,"AS")
    X(1):  STATUS  (704.002,.02)  (Subscr 1)  (Len 30)  (forwards)
  • RECORD INDEXES:  PURGE (#909)
.03 MAPPING_TABLE 0;3 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>50!($L(X)<1) X
  • LAST EDITED:  MAR 24, 2009
  • HELP-PROMPT:  Answer must be 1-50 characters in length.
  • DESCRIPTION:  
    This field contains a copy of the ID field(#.01) in the TERM_MAPPING_TABLE file(#704.108).  It is used to determine which mapping table to use when translating the HL7 message (MESSAGE_ID(field(#.01)) into observations.
.04 HL7_MESSAGE_ADMINISTRATION 0;4 POINTER TO HL7 MESSAGE ADMINISTRATION FILE (#773)
************************REQUIRED FIELD************************
HL7 MESSAGE ADMINISTRATION(#773)

  • LAST EDITED:  MAR 24, 2009
  • HELP-PROMPT:  Answer with HL7 MESSAGE ADMINISTRATION identifier.
  • DESCRIPTION:  
    This field identifies this Clinical Flowsheets HL7 message (MESSAGE_ID field (#.01)) with an entry in the HL7 Message Administration File (#773).
.05 HL7_MESSAGE_TEXT 0;5 POINTER TO HL7 MESSAGE TEXT FILE (#772)
************************REQUIRED FIELD************************
HL7 MESSAGE TEXT(#772)

  • LAST EDITED:  MAR 24, 2009
  • HELP-PROMPT:  Answer with an HL7 MESSAGE TEXT identifier.
  • DESCRIPTION:  
    This field identifies this Clinical Flowsheets HL7 message (MESSAGE_ID field (#.01)) text with an entry in the HL7 MESSAGE TEXT File (#772).
.06 PATIENT 0;6 POINTER TO PATIENT FILE (#2) PATIENT(#2)

  • LAST EDITED:  MAR 24, 2009
  • HELP-PROMPT:  Answer with a PATIENT identifier.
  • DESCRIPTION:  
    This is the patient supported by the Clinical Flowsheets HL7 message (MESSAGE_ID field(#.01)).
.07 STUDY_REFERENCE_NBR 0;7 POINTER TO CP TRANSACTION FILE (#702) CP TRANSACTION(#702)

  • LAST EDITED:  MAR 24, 2009
  • HELP-PROMPT:  Answer with CP TRANSACTION identifier.
  • DESCRIPTION:  
    This field identifies the Clinical Flowsheets HL7 message (MESSAGE_ID field(#.01)) with a CP TRANSACTION File (#702) entry.
.08 MESSAGE_DATE_TIME 0;8 DATE

  • INPUT TRANSFORM:  S %DT="ESTX" D ^%DT S X=Y K:X<1 X
  • LAST EDITED:  MAR 24, 2009
  • HELP-PROMPT:  (No range limit on date)
  • DESCRIPTION:  
    This is the date/time the HL7 message (MESSAGE_ID field(#.01)) was created as reported by the HL7 system.
.09 PROCESSED_TIMESTAMP 0;9 DATE

  • INPUT TRANSFORM:  S %DT="ESTX" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  MAR 24, 2009
  • HELP-PROMPT:  Answer with TIMESTAMP the message was processed.
  • DESCRIPTION:  This is the date/time the HL7 message (MESSAGE_ID field(#.01))
    was processed as reported by the HL7 system.
    WRITE AUTHORITY:
  • RECORD INDEXES:  PURGE (#909)
.11 REPORTED_LOCATION 1;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>250!($L(X)<1) X
  • LAST EDITED:  MAR 24, 2009
  • HELP-PROMPT:  Answer must be 1-250 characters in length.
  • DESCRIPTION:  This is raw-data as extracted from the HL7 message (MESSAGE_ID field(#.01)). This should be location identifying data that can be used to locate the source of the HL7 message (MESSAGE_ID field(#.01)).
    A sample REPORTED LOCATION could be  "3AS|3XX-N|".
.21 REPORTED_PATIENT 2;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>250!($L(X)<1) X
  • LAST EDITED:  MAR 24, 2009
  • HELP-PROMPT:  Answer must be 1-250 characters in length.
  • DESCRIPTION:  This is raw-data extracted from the HL7 message (MESSAGE_ID field (#.01)). This should be patient identifying data used to determine which patient the HL7 message (MESSAGE_ID field(#.01)) supports.
    A sample REPORTED PATIENT could be:
    "CPFLOWSHEETS,PATIENT1|666262463|2550401|X|" .
.31 REPORTED_INSTRUMENT 3;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>250!($L(X)<1) X
  • LAST EDITED:  MAR 24, 2009
  • HELP-PROMPT:  Answer must be 1-250 characters in length.
  • DESCRIPTION:  This is raw-data extracted from the HL7 message (MESSAGE_ID field (#.01)). This should be instrument identifying data used to determine the source-device of the HL7 message (MESSAGE_ID field(#.01)).
    A sample REPORTED INSTRUMENT could be "DEVICEX" .

External References

Name Field # of Occurrence
^%DT .08+1, .09+1

Global Variables Directly Accessed

Name Line Occurrences  (* Changed,  ! Killed)
^MDC(704.002 - [#704.002] IXASSL+1*, IXASKL+1!, IXASKEIC+1!, IXPKSL+1*, IXPKKL+1!, IXPKKEIC+1!, IXPURGESL+1*, IXPURGEKL+1!, IXPURGEKEIC+1!

Local Variables

Legend:

>> Not killed explicitly
* Changed
! Killed
~ Newed

Name Field # of Occurrence
>> %DT .08+1*, .09+1*
>> DA IXASSL+1, IXASKL+1, IXPKSL+1, IXPKKL+1, IXPURGESL+1, IXPURGEKL+1
X IXASSL+1, IXASKL+1, IXPKSL+1, IXPKKL+1, .01+1!, .03+1!, .08+1*!, .09+1*!, .11+1!, .21+1!
, .31+1!
X(1 IXPURGESL+1, IXPURGESCC+1, IXPURGEKL+1, IXPURGEKCC+1
X(2 IXPURGESL+1, IXPURGEKL+1
>> Y .08+1, .09+1
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries |  External References |  Global Variables Directly Accessed |  Local Variables |  All