Procedure Classification

Before you can use the ExecuteMultivariate function, Validation and Derivation Procedures must be categorized in Oracle Clinical. This step lets the function, ExecuteMultivariate identify the Procedures to execute in different circumstances.

Procedures are classified by the Execution Context attribute. A field for the attribute is displayed in the Oracle Clinical Procedures forms. Although this attribute can be entered for both pre-V3.1- and V3.1-style Procedures, only V3.1-style Procedures can be called by ExecuteMultivariate. The Execution Context does not affect batch validation processing.

This attribute's value should be chosen based on the Procedure's purpose and its usefulness in raising multivariate discrepancies for timely feedback during data entry. While the value defaults to OFF-LINE, V3.1-style Procedures can change it to either ON-LINE/DCM or ON-LINE.

See the following:

• Using Execution Context
  
• Relationship Between Procedure Definition and Procedure Execution
  

Using Execution Context

These sections describe the values for the Execution Context attribute. An API-only argument, SINGLE, is also described because it affects Procedure classification.

See the following:

• ON-LINE/DCM
  
• ON-LINE
  
• OFF-LINE
  
• SINGLE
  

ON-LINE/DCM

Procedures should be classified as ON-LINE/DCM when they are suitable for DCM-targeted types of validation to be invoked— for instance, at the completion of data entry for a given patient's DCM. Procedures with aggregate-only question groups, which have no primary reference DCM, cannot be classified as ON-LINE/DCM.

Calling ExecuteMultivariate with an ON-LINE/DCM Execution Context causes a specific DCM to be supplied in the API call. Procedures are then targeted for execution on the basis of a match on:

• Execution Context
• The Procedure primary reference question group DCM

  Note:

  When ExecuteMultivariate is called with an ON-LINE Execution Context, Procedures classified as ON-LINE/DCM are automatically executed, regardless of their primary reference question group DCM.

ON-LINE

An ON-LINE classification indicates the Procedure is suited to being invoked after a larger unit of work (two or more DCMs) is completed for the patient — regardless of the Procedure primary reference question group DCM. Procedures classified as ON-LINE or ON-LINE/DCM are automatically executed when ExecuteMultivariate is called with an ON-LINE Execution Context.

OFF-LINE

Procedures classified as OFF-LINE (the default) are not executed when the API Execution Context argument is either ON-LINE or ON-LINE/DCM. They are typically appropriate for the following circumstances:

• Batch processing
• Execution in batch validation
• Execution via the Execute Single Procedure menu option

SINGLE

An API-only argument, SINGLE, signifies that a specific Procedure is to be executed; the Procedure ID and version are supplied as API arguments in this case. When ExecuteMultivariate is called with the Execution Context of SINGLE, the match on Procedure classification is bypassed and the requested Procedure executed.

Relationship Between Procedure Definition and Procedure Execution

Procedures can have dependencies, such as using the results of derivation for subsequent validation. The Procedure Definition form enforces the restriction that a Procedure can only be flagged for a particular Execution Context if all Procedures upon which it is dependent are also in the same context or in a "lesser" context. This means that "related" Procedures must be guaranteed to execute in tandem.

The following tables shows, for six sample Procedures, whether the Procedure will be selected for execution in each context.

Procedure Definition	Procedure Execution — On-Line Processing API Execution Context	Procedure Execution — On-Line Processing API Execution Context	Procedure Execution — On-Line Processing API Execution Context	Procedure Execution — Off-Line Processing	Procedure Execution — Off-Line Processing
-	ON-LINE/ DCM DEMOG	ON-LINE	Single Procedure B	Batch Validation	Execute Single Procedure B
Proc: A, Primary Ref DCM: DEMOG, Execution Context: ON-LINE/DCM	Selected	Selected	Not selected	Selected	Not selected
Proc: B, Primary Ref DCM: DCM48, Execution Context: ON-LINE/	Not selected	Selected	Selected	Selected	Selected
Proc: C, Primary Ref DCM: DCM48, Execution Context: OFF-LINE/	Not selected	Not selected	Not selected	Selected	Not selected
Proc: D, Primary Ref DCM: DEMOG, Execution Context: ON-LINE/DCM	Selected	Selected	Not selected	Selected	Not selected
Proc: E, Primary Ref DCM: VITAL_SIGNS, Execution Context: OFF-LINE	Not selected	Not selected	Not selected	Selected	Not selected
Proc: F , Primary Ref DCM: VITAL_SIGNS, Execution Context: ON-LINE	Not selected	Selected	Not selected	Selected	Not selected

For instance, if Procedure X uses derived values from Procedure Y the possible classification combinations between the two Procedures are shown below. When the derivation Procedure Y’s definition is on-line/DCM, Validation Procedure X’s definition is "Selected" for all three contexts: ON-LINE/DCM, ON-LINE, and OFF-LINE. When Procedure Y is on-line, Procedure X’s defintion is "Not selected" for ON-LINE/DCM and "Selected" for ON-LINE and OFF-LINE. When Procedure Y’s definition is off-line, Procedure X’s definition is "Not selected" for both ON-LINE/DCM and ON-LINE, and "Selected" for OFF-LINE.

Derivation Procedure Y Definition	Validation Procedure X Definition ON-LINE/DCM	Validation Procedure X DefinitionON-LINE	Validation Procedure X DefinitionOFF-LINE
on-line/DCM	Selected	Selected	Selected
on-line	Not selected	Selected	Selected
off-line	Not selected	Not selected	Selected