You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Composite SearchParameter’s can only be composed out of the following 4 types of basic SearchParameter definitions: STRING, TOKEN, DATE, QUANTITY
But now it is possible to create composite SearchParameter with any type.
Steps To Reproduce
Create a SearchParameter based on a "type": "token".
Create another SearchParameter based on a "type": "reference".
Create a Composite SearchParameter which uses both of the above in its "component" definition.
If you try and use this Composite SearchParameter in a GET Request, you will get the following ERROR Response:
{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "processing",
"diagnostics": "HAPI-1204: Don't know how to handle composite parameter with type of REFERENCE"
}
]
}
GET {Server_URL}//Observation?patient-code:code$loinc|8302-2,value$1409
Actual result
Composite search parameter with "reference" component created successfully, but composite search query fails in runtime. Expected behavior
Creation of Composite search parameter with "reference" component should be prohibited.
The text was updated successfully, but these errors were encountered:
Composite SearchParameter’s can only be composed out of the following 4 types of basic SearchParameter definitions: STRING, TOKEN, DATE, QUANTITY
But now it is possible to create composite SearchParameter with any type.
Steps To Reproduce
Requests Example:
Actual result
Composite search parameter with "reference" component created successfully, but composite search query fails in runtime.
Expected behavior
Creation of Composite search parameter with "reference" component should be prohibited.
The text was updated successfully, but these errors were encountered: