Global: ^IBE(357.6

The name of the Package Interface. The name should be preceded with the namespace of the package.

1)= S ^IBE(357.6,"B",$E(X,1,30),DA)=""

2)= K ^IBE(357.6,"B",$E(X,1,30),DA)

1)= N IBDXE S IBDXE=$E(X,$F(X," "),40) S:$A(IBDXE)<33 IBDXE=X S ^IBE(357.6,"E",IBDXE,DA)=""

2)= N IBDXE S IBDXE=$E(X,$F(X," "),40) S:$A(IBDXE)<33 IBDXE=X K ^IBE(357.6,"E",IBDXE,DA)

For package interfaces that are output routines the name has the custodial package's name space as a prefix. This cross-reference removes that prefix. It is used to improve the display of output routines for the user.

The entry point in the routine that should be called.

The routine that should be called.

This is a free text pointer to the package file. It serves only to document the custodial package of the data.

1)= S ^IBE(357.6,"C",$E(X,1,30),DA)=""

2)= K ^IBE(357.6,"C",$E(X,1,30),DA)

This field is used in the batch printing of encounter forms. The purpose is to avoid recomputing fields whose data does not change from patient to patient.

and transmits the data to the appropriate package. Enter 2 for DISPLAY if the interface retrieves data for display to a form.  Enter 3 for SELECTION if the interface is for building a list to display

to a form.  Enter 4 if the interface is for printing a report.

If the ACTION TYPE is SELECTION then the data type must be a record and the first piece must be the ID use to uniquely identify the selection.

A single value is a string without pieces. A record is a set of strings concatenated together with "^" separating the pieces. A list is an indefinite number of values, each numbered, each containing the same type of

information. A word processing data type will be in FM format.  If the ACTION TYPE is SELECTION then the data type must be record.

This field is used to determine what should happen if the data does not fit in the space allocated to it on the form. If answered YES the data will be printed on another page.

This field should be set to YES if the interface is available, NO if it is not available. Interfaces that are not available are not called.

Summary to print. The process of printing Health Summaries dos not use the fields ENTRY POINT or ROUTINE, since all Health Summaries are printed in the same way.

This identifies the Health Summary that should be printed when this Package Interface is invoked. It should be null unless the HEALTH SUMMARY? field #.1 is coded YES.

Package Interfaces that are developed for national use will be documented as being part of the toolkit.

Used to map scanned data to DHCP.

This is used to indicate whether the interface is used to build selection lists at print time.

subscript, but, to maintain compatibilty, output routines must set this field to YES if DFN is not to be used as a subscript. This field has no effect on other types of interfaces.

sense to allow a multiple choice question to point to vitals, which is used to input data such as temperature and blood pressure.

as it appears on the form will be used as the provider narrative.

Generally only dianosis and clinical lexicon entries will want this field set to Yes.

recommended for user who are scanning diagnosis entries and trying to add entries to the Patients Problem list.

The primary purpose of this field is to allow sites who have built selection lists using the ICD9 Diagnosis file to map each entry to the clinical lexicon.  The Problem List EP has recommended that each problem added to

the problem list be associated with a clinical lexicon entry.

Field used to determine if a data qualifier is required for this input interface.

If this package interface is for display of clinical reminders answer yes, otherwise answer no.

ASK FOR CPT MODIFIERS field will be used when selecting CPT codes.  If answered "YES" and data is a procedure, CPT Modifiers should be asked during Forms Design and Manual Data Entry.

Should describe the data being exchanged by the package interface.

Should be a descriptive name of the first field in the record returned by the interface.

The maximum length of the first field of the record returned by the interface.

The recommended header will be used as the default when designing a form.

This is used only for selection type interfaces. If NO, then the value can not be displayed to the encounter form.  The first piece must contain the unique id of the selection.

Applies to selection and input routines. Determines whether selections appearing on selection lists and choices in a multiple choice field will be exported along with the form that they appear on. The import/export utility

will not resolve pointers, so if the id used by the package interface is a pointer that differs between sites this field should contain NO.

This field is used to create a KWIC index for this file. The purpose is to assist the user in locating the package interface he needs to display a particular item of data to a form.

1)= S %1=1 F %=1:1:$L(X)+1 S I=$E(X,%) I "(,.?! '-/&:;)"[I S I=$E($E(X,%1,%-1),1,30),%1=%+1 I $L(I)>2,^DD("KWIC")'[I S ^IBE(357.6,"D",I,DA)=""

2)= S %1=1 F %=1:1:$L(X)+1 S I=$E(X,%) I "(,.?! '-/&:;)"[I S I=$E($E(X,%1,%-1),1,30),%1=%+1 I $L(I)>2 K ^IBE(357.6,"D",I,DA)

This index is meant to assist the user in locating the correct package interface needed to display a particular item of data to a form.

This code will be executed after the PROTECTED VARIABLES are newed, but before the interface routine is called.

WRITE AUTHORITY:  @

This code will be executed after the interface routine is called.  The effect of the NEW done on the PROTECTED VARIABLES is still in effect.

WRITE AUTHORITY:  @

VARIABLES should not also be PROTECTED VARIABLES. If an interface routine changes a required variable, however, there is a way to protect it.  Supposing, for example, DFN is killed by the interface. This will protect it:

PROTECTED VARIABLE:   IBDFN

ENTRY ACTION:  S IBDFN=DFN

EXIT ACTION:   S DFN=IBDFN

The interface may require inputs. This field is a list of the required local variables. The interface will not be called unless the variables are determined to exist.

Used to transform X, the identifier stored with the form object, to the form that should be passed to the PCE Device Interface Module. It may, for example, transform a code to an ien.

WRITE AUTHORITY:  @

This should provide some help to the user who is trying to enter a value associated with a bubble.

of the entry in the selection list. Xecuting this field will result in X being killed if the value is not valid. This is used by the maintanance utility, for example, to find CPT codes that have been inactivated.

WRITE AUTHORITY:  @

The node used to pass the data to PCE, using the PCE DEVICE INTERFACE MODULE.

The piece in the PXCA node used to pass the input value.

The piece in the PCXA node used to pass the text displayed on the form.

The piece on the node specified by the PCE DIM that the header is mapped to.

The piece of the PXCA node where the data modifier belongs.

An entry in this field indicates which piece of the array the quantity should be passed on when sending data to PCE.

This mulitiple contains the list of qualifiers that may apply to the data.

This transform should set Y, the value to be passed to the PCE Device Interface Module (DIM), to a value that is suitable for display. It may, for example, change an ien to a code.

WRITE AUTHORITY:  @

For interfaces that return records, this multiple stores information on the fields, other than the first field.

"WRITE":    D EN^DDIOL("   PIECE="_$P(^(0),U,3),"","?0")

For selection interfaces, this field determines whether a narrative is allowed by the PCE Generic Device Interface.

This determines, among other things, how much space to allocate for the narrative.

Used to label the narrative field.

For selectin interfaces this determines whether a value, other than a narrative, can be entered.

For selection interfaces this determines, among other things, the data type of the value to be entered.

Used to label the primary value field.

For selection interfaces, this determines whether 'quantity' should be asked at form development time to pass multiple occurrences of a selection to PCE.

selection of the code if the entry is edited.

perhaps the code.  2) Set IBLABEL to a suitable label for the choice.  3) Set IBID to an identifier. The identifier should ideally be exportable, meaning the same from site to site. This usually means a coded value rather

than an ien. The identfier should match that of a corresponding selection interface, if there is one.

WRITE AUTHORITY:  @

This field should only be completed for input package interfaces.  This code will be executed to provide quick data entry for a user trying to input data for a form.  It is expected that the output of this field will be

used to format the PXCA array prior to calling PCE to file the data for the encounter.

Developers writing routines for this entry should provide a roll and scroll interface for manaul entry of items only on the form.

WRITE AUTHORITY:  @

what is to be passed, to the user for verification.

WRITE AUTHORITY:  @

Qualifier to pass as the VALUE.  This is used mostly for YES/NO Data Qualifiers, where the value may be a question, and the Data Qualifier Value, if bubbled, is the value that must be placed on the PCE DIM NODE.

Ultimately, the code should return a value that will be used as the PCE DIM PIECE VALUE.  If the return value is null, the original PCE DIM PIECE VALUE field will be used to determine the piece location to pass the VALUE

on.

WRITE AUTHORITY:  @