This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
Logical Model FilterComponent
{
"resourceType": "StructureDefinition",
"id": "FilterComponent",
"url": "{http://www.omg.org/spec/CTS2/1.1/Core}FilterComponent",
"name": "FilterComponent",
"display": "CTS2.FilterComponent",
"status": "draft",
"publisher": "Generated by Xsd-to-FHIR",
"contact": [
{
"name": "Visit the Github repository for more information",
"telecom": [
{
"system": "other",
"value": "https://github.com/cts2/CTS2-to-FHIR"
}
]
}
],
"date": "2016-02-08T19:11:02-07:00",
"description": "A restriction on an attribute, property or special field",
"fhirVersion": "1.4.0",
"kind": "logical",
"abstract": false,
"baseDefinition": "{http://www.omg.org/spec/CTS2/1.1/Core}ComponentReference",
"snapshot": {
"element": [
{
"path": "FilterComponent",
"short": "FilterComponent",
"definition": "A restriction on an attribute, property or special field",
"min": 0,
"max": "*",
"base": {
"path": "{http://www.omg.org/spec/CTS2/1.1/Core}ComponentReference",
"min": 0,
"max": "*"
},
"type": [
{
"code": "ComponentReference"
}
]
},
{
"path": "FilterComponent.matchAlgorithm",
"name": "matchAlgorithm",
"short": "the algorithm to be used for testing the referenced component",
"definition": "the algorithm to be used for testing the referenced component. Examples might include \"starts with\", \"regular expression match\", \"exists\", \"inRange\", etc. NOTE: The CTS2 specification\n\t\t\t\t\t\t\t\tneeds to establish a core set of match algorithms that all compliant implementations must support.",
"min": 1,
"max": "1",
"type": [
{
"code": "MatchAlgorithmReference"
}
]
},
{
"path": "FilterComponent.matchValue",
"name": "matchValue",
"short": "the value to be used in comparison",
"definition": "the value to be used in comparison. The structure and format of matchValue depends on the specific matchAlgorithm. As an example, a \"startsWith\" algorithm would be plain text, a\n\t\t\t\t\t\t\t\t\"regularExpression\" algorithm would have a regular expression while an \"exists\" algorithm would have nothing in the matchValue attribute.",
"min": 0,
"max": "1",
"type": [
{
"code": "String"
}
]
}
]
}
}
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.