Please see all the "disclaimers" from the prior post on Quality Guidelines.  I hate repeating myself.

 

This set of shortest interview guidelines is just a draft start.  It requires community feedback.  It has been created because I noticed a pattern where clients ask how to use OPA to shorten interviews (especially screening for eligibility.) 

 

It needs work, but is a start of guidance specific to that problem.  See the attached word document.  Provide constructive critique.  Take it or leave it. 

 

It would be nice to post a better document in another month or two that contained positive community feedback.

 

Shortest Interview Checklist

Use the following checklist for guideline compliance. Scoring is utilized as a quality assessment to measure maturity of an OPA implementation for shortest interview.

Scoring is as follow:

0 = Not in use

1 = Partially available and/or partially used by the project

2 = Available and in-use by the project

Quality Check

Analysis

OPA interviews follow the whitepaper "Oracle Policy Automation Best Practice Guide for Policy Modelers" provided by Oracle.

0 / 1 / 2

There is a single top-level interview goal for the primary determination. No other goals are defined in the interview.

0 / 1 / 2

Until the primary determination is made, all attributes collected in the interview are conditions relevant to the single top-level interview goal or provide many default values to conditions for the single top-level goal.

0 / 1 / 2

Attributes where base data is not going to be kept or otherwise queried are combined.

0 / 1 / 2

Screens, booleans, and containers should show if "control collects relevant information".

0 / 1 / 2

Any possible shortcut rules have been created.

0 / 1 / 2

Every question defaults to the most likely value or provides hint text.

0 / 1 / 2

The base attributes most responsible for the value of the top-level interview goals are collected first.

0 / 1 / 2

Screens / questions of interest to the business but not the determination are put after the questions for the primary determination.

0 / 1 / 2

Projects pay additional attention to the time spent per screen and interview duration charts available on the OPA hub after the August 2017 release of OPA. This data is used periodically to revise attribute collection.

0 / 1 / 2

Use is maximized for "hide" for all controls.

0 / 1 / 2

Answers are restricted to small sets and rearranged so that earlier attributes can restrict later attributes.

0 / 1 / 2

The default number of entity instances is provided dynamically.

0 / 1 / 2