alex_empallo
02/18/2025, 8:36 PMInvalid include value 'Encounter': must be of the form ResourceType:search-parameter
This happens sporadically across different actions in our app (retrying the request again often works). The affected code isn't interacting with any Encounter resource at all.
Is anyone else seeing this? Any insight into what might be causing it?rahul1
02/19/2025, 7:14 AM_include search.
https://www.medplum.com/docs/search/includes#_include-and-_revincluderahul1
02/19/2025, 7:14 AMalex_empallo
02/19/2025, 4:04 PM_include parameter. The same code (several different unrelated pieces of code that make calls to medplum) that did not generate this error before suddenly began generating this error yesterday.alex_empallo
02/19/2025, 4:37 PMXHRPOST
https://api.medplum.com/fhir/R4/Subscription
[HTTP/2 400 39ms]
{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "invalid",
"details": {
"text": "Invalid include value 'Encounter.subject': must be of the form ResourceType:search-parameter"
}
}
],
"extension": [
{
"url": "https://medplum.com/fhir/StructureDefinition/tracing",
"extension": [
{
"url": "requestId",
"valueId": "f04ae746-0726-4ba2-887d-4a7eb7608948"
},
{
"url": "traceId",
"valueId": "1-67b60539-04acc8ef5a0965a6357fc94d"
}
]
}
]
}
Immediately followed by this error in console:
Invalid include value 'Encounter.subject': must be of the form ResourceType:search-parameter <anonymous code>:1:145535
overrideMethod <anonymous code>:1
...alex_empallo
02/19/2025, 4:38 PMreqeust that results in the HTTP 400 error:
{
"resourceType": "Subscription",
"status": "active",
"reason": "WebSocket subscription for Practitioner/4afd4fba-bb7c-4f9c-99b4-3682f59b4bcb",
"criteria": "Communication?recipient=Practitioner/4afd4fba-bb7c-4f9c-99b4-3682f59b4bcb",
"channel": {
"type": "websocket"
}
}alex_empallo
02/21/2025, 6:47 PM