Unable to create custom search parameter for Careplan medicaldevice

[sasireha]

Description
I tried to create the following custom search parameter for CarePlan but server returns bad request error.

{
   "resourceType": "SearchParameter",
   "id": "careplan-medicaldevice",
   "url": "http://nictiz.nl/fhir/SearchParameter/careplan-medicaldevice",
   "version": "1.0.0",
   "name": "careplan-medicaldevice",
   "status": "active",
   "publisher": "Nictiz",
   "contact": `[`
       {
           "name": "Nictiz",
           "telecom": [
               {
                   "system": "email",
                   "value": "info@nictiz.nl",
                   "use": "work"
               }
           ]
       }
   ],
   "purpose": "To search on a DeviceUseStatement resource, referenced from an extension in CarePlan. Main purpose is to use this search parameter for including DeviceUseStating resouces in the result for a search on CarePlan.",
   "code": "medicaldevice",
   "base": [
       "CarePlan"
   ],
   "type": "reference",
   "description": "To alow a search (_include) on the materials used in nursing procedures, such as bandages.",
   "expression": "CarePlan.activiy.detail.extension('http://nictiz.nl/fhir/StructureDefinition/extension-medicaldevice')"
 }

FHIR Version
Stu3

Data provider
CosmosDB

Expected behavior
Should be able to create the custom search parameter with the url 'http://nictiz.nl/fhir/SearchParameter/careplan-medicaldevice'

Actual behavior
Fhir server returns the following error message

{
    "resourceType": "OperationOutcome",
    "id": "1b3598f0-f3af-40b7-8739-41b121106d80",
    "issue": [
        {
            "severity": "error",
            "code": "not-supported",
            "diagnostics": "The search parameter with definition URL 'http://nictiz.nl/fhir/SearchParameter/careplan-medicaldevice' is not supported."
        },
        {
            "severity": "error",
            "code": "exception",
            "diagnostics": "An error occurred updating the custom search parameter.  The issue must be resolved and the update resubmitted to be applied."
        }
    ]
}

AB#101795

[brendankowitz]

The expression needs to be a type that can converted from the Model Type to a Search type, so it can be indexed. In the example above the expression ends with type Extension.

If you take http://hl7.org/fhir/us/core/STU3.1.1/SearchParameter-us-core-race.html for example, it specifies Patient.extension.where(url = 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-race').extension.value.code which would be able to be converted to a token search type.

If the extension data was similar to:

"extension":  [
                    {
                        "url": "http://nictiz.nl/fhir/StructureDefinition/extension-medicaldevice",
                        "valueReference": {
                            "reference": "DeviceUseStatement/zib-wound-medicaldevice-01",
                            "display": "Verband"
                        }
                    }
                ]

The parser would need something like the following to detect support correctly:
CarePlan.activiy.detail.extension('http://nictiz.nl/fhir/StructureDefinition/extension-medicaldevice').value

[sasireha]

Thanks for the update!
I modified the expression as you mentioned but still I get the same error.

{
    "resourceType": "OperationOutcome",
    "id": "f84282eb-ad9e-4618-bffd-d993b7a93bb9",
    "issue": [
        {
            "severity": "error",
            "code": "not-supported",
            "diagnostics": "The search parameter with definition URL 'http://nictiz.nl/fhir/SearchParameter/careplan-medicaldevice' is not supported."
        },
        {
            "severity": "error",
            "code": "exception",
            "diagnostics": "An error occurred updating the custom search parameter.  The issue must be resolved and the update resubmitted to be applied."
        }
    ]
}

[CaitlinV39]

Can you send the updated search parameter you posted?

[sasireha]

Here it is

{
                "resourceType": "SearchParameter",
                "id": "careplan-medicaldevice",
                "url": "http://nictiz.nl/fhir/SearchParameter/careplan-medicaldevice",
                "version": "1.0.0",
                "name": "careplan-medicaldevice",
                "status": "active",
                "publisher": "Nictiz",
                "contact": [
                    {
                        "name": "Nictiz",
                        "telecom": [
                            {
                                "system": "email",
                                "value": "info@nictiz.nl",
                                "use": "work"
                            }
                        ]
                    }
                ],
                "purpose": "To search on a DeviceUseStatement resource, referenced from an extension in CarePlan. Main purpose is to use this search parameter for including DeviceUseStating resouces in the result for a search on CarePlan.",
                "code": "medicaldevice",
                "base": [
                    "CarePlan"
                ],
                "type": "reference",
                "description": "To alow a search (_include) on the materials used in nursing procedures, such as bandages.",
                "expression": "CarePlan.activiy.detail.extension('http://nictiz.nl/fhir/StructureDefinition/extension-medicaldevice').value"
            }

[Ivanidzo4ka]

Let me recall my previous statement...
Main reason why it's not working:
CarePlan.activiy is misspelled it should be CarePlan.activity

[sasireha]

Thanks I have corrected the spelling as mentioned but I get a different error now. I have provided value for all the mandatory properties, I'm not sure what I'm missing still.

{
                "resourceType": "SearchParameter",
                "id": "careplan-medicaldevice",
                "url": "http://nictiz.nl/fhir/SearchParameter/careplan-medicaldevice",
                "version": "1.0.0",
                "name": "careplan-medicaldevice",
                "status": "active",
                "publisher": "Nictiz",
                "contact": [
                    {
                        "name": "Nictiz",
                        "telecom": [
                            {
                                "system": "email",
                                "value": "info@nictiz.nl",
                                "use": "work"
                            }
                        ]
                    }
                ],
                "purpose": "To search on a DeviceUseStatement resource, referenced from an extension in CarePlan. Main purpose is to use this search parameter for including DeviceUseStating resouces in the result for a search on CarePlan.",
                "code": "medicaldevice",
                "base": [
                    "CarePlan"
                ],
                "type": "reference",
                "description": "To alow a search (_include) on the materials used in nursing procedures, such as bandages.",
                "expression": "CarePlan.activity.detail.extension('http://nictiz.nl/fhir/StructureDefinition/extension-medicaldevice').value"
            }

{
    "resourceType": "OperationOutcome",
    "id": "a7be835d-3d8e-4e99-974f-daee7060ba99",
    "issue": [
        {
            "severity": "error",
            "code": "exception",
            "diagnostics": "An error occurred updating the custom search parameter.  The issue must be resolved and the update resubmitted to be applied."
        },
        {
            "severity": "error",
            "code": "exception",
            "diagnostics": "Value cannot be null. (Parameter 'uriString')"
        }
    ]
}

[CaitlinV39]

@CaitlinV39

[CaitlinV39]

@rotodd Would you mind taking a look at this one?

[sasireha]

Hi, Is there any update on this issue?

[CraigP68]

AB#87251

[EXPEkesheth]

@sasireha - are you still facing the issue? This is a good reference page : https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/how-to-do-custom-search.

Please let us know if you have additional questions. If we have no response - this issue will be closed (given it was created more than year ago)

[EXPEkesheth]

Closing the issue due to no response