Describes a required data item for evaluation in terms of the type of data, and optional code or date-based filters of the data.
= Must Support, = Is Modifier, = QiCore defined extension
Field | Card. | Type | Description |
---|---|---|---|
type | 1..1 | String | The type of the required data, specified as the type name of a resource. For profiles, this value is set to the type of the base resource of the profile. |
profile | 0..* | String | The profile of the required data, specified as the uri of the profile definition. |
mustSupport | 0..* | String | Indicates that specific elements of the type are referenced by the knowledge module and must be supported by the consumer in order to obtain an effective evaluation. This does not mean that a value is required for this element, only that the consuming system must understand the element and be able to provide values for it if they are available. Note that the value for this element can be a path to allow references to nested elements. In that case, all the elements along the path must be supported. |
codeFilter | 0..* | Element | Code filters specify additional constraints on the data, specifying the value set of interest for a particular element of the data. |
codeFilter.id | 0..1 | String | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
codeFilter.extension | 0..* | Extension | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
codeFilter.path | 1..1 | String | The code-valued attribute of the filter. The specified path must be resolvable from the type of the required data. The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements. Note that the index must be an integer constant. The path must resolve to an element of type code, Coding, or CodeableConcept. |
codeFilter.valueSet[x] | 0..1 | String | ValueSet | The valueset for the code filter. The valueSet and value elements are exclusive. If valueSet is specified, the filter will return only those data items for which the value of the code-valued element specified in the path is a member of the specified valueset. |
codeFilter.valueCode | 0..* | String | The codes for the code filter. Only one of valueSet, valueCode, valueCoding, or valueCodeableConcept may be specified. If values are given, the filter will return only those data items for which the code-valued attribute specified by the path has a value that is one of the specified codes. |
codeFilter.valueCoding | 0..* | Code | The Codings for the code filter. Only one of valueSet, valueCode, valueConding, or valueCodeableConcept may be specified. If values are given, the filter will return only those data items for which the code-valued attribute specified by the path has a value that is one of the specified Codings. |
codeFilter.valueCodeableConcept | 0..* | Concept | The CodeableConcepts for the code filter. Only one of valueSet, valueCode, valueConding, or valueCodeableConcept may be specified. If values are given, the filter will return only those data items for which the code-valued attribute specified by the path has a value that is one of the specified CodeableConcepts. |
dateFilter | 0..* | Element | Date filters specify additional constraints on the data in terms of the applicable date range for specific elements. |
dateFilter.id | 0..1 | String | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
dateFilter.extension | 0..* | Extension | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
dateFilter.path | 1..1 | String | The date-valued attribute of the filter. The specified path must be resolvable from the type of the required data. The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements. Note that the index must be an integer constant. The path must resolve to an element of type dateTime, Period, Schedule, or Timing. |
dateFilter.value[x] | 0..1 | DateTime | Interval<DateTime> | Duration | The value of the filter. If period is specified, the filter will return only those data items that fall within the bounds determined by the Period, inclusive of the period boundaries. If dateTime is specified, the filter will return only those data items that are equal to the specified dateTime. If a Duration is specified, the filter will return only those data items that fall within Duration from now. |