Expression Set Options Input

Input representation of the options for executing an expression set.

JSON Example

1{
2  "inputs": [
3    {
4      "age": "25",
5      "state": "CA",
6      "PatientId": "001xx000003GYjnAAG"
7    }
8  ],
9  "options": {
10    "effectiveDate": "2022-12-03T10:15:30Z",
11    "useDatesOnly": "true",
12    "actionContextCode": "9QLxx0000004C92GAE",
13    "explainabilitySpecName": "ES_One_Explainability"
14  }
15}

Properties

Name	Type	Description	Required or Optional	Available Version
`actionContextCode`	String	The code of the action context used to log explainability for a specific execution of an expression set. Note: To exclude decision explanations for expression set version steps from action logs, ensure that you exclude the `actionContextCode` and `explainabilitySpecName` properties from the payload.	Optional	55.0
`effectiveDate`	String	The date from which an expression set comes into effect. The date format is yyyy-mm-dd’T’hh:mm:ss’Z. Note: Multiple versions of an expression set can exist with different date ranges. For example, Version 1 is effective before December 2019, and Version 2 is effective from January 2020 to the present. If you specify `effectiveDate` as “2019-03-15T00:00:00Z”, Version 1 is executed. If you do not specify `effectiveDate`, the currently active version, Version 2, is executed.	Optional	55.0
`explainabilitySpecName`	String	The name of the explainability specification that is used to log explainability for a specific execution of an expression set. Note: To exclude decision explanations for expression set version steps from action logs, ensure that you exclude the `actionContextCode` and `explainabilitySpecName` properties from the payload.	Optional	55.0
`useDatesOnly`	String	Specifies that only the date portion (yyyy-mm-dd) of the value of effectiveDate field is to be used at the time of execution.	Optional	55.0
`versionNumber`	String	The version number of the expression set version record.	Optional	55.0