[ 
https://issues.apache.org/jira/browse/CAMEL-18004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jawad Ahmad updated CAMEL-18004:
--------------------------------
    Summary: Camel FHIR - Custom Header and Query Parameters  (was: Camel FHIR 
- Custom Header Parameters)

> Camel FHIR - Custom Header and Query Parameters
> -----------------------------------------------
>
>                 Key: CAMEL-18004
>                 URL: https://issues.apache.org/jira/browse/CAMEL-18004
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-fhir
>    Affects Versions: 3.16.0
>            Reporter: Jawad Ahmad
>            Priority: Major
>
> We are trying to integrate NHS FHIR API with our Salesforce instance. We are 
> connecting with NHS using FHIR component. NHS Payloads are on FHIR R4 with UK 
> Extensions.
> The issue we are facing is that, apart from standard extra params, NHS API 
> except for a few custom parameters in requests as well. There seems to be no 
> way to add those in FHIR operations, I was able to add independent headers 
> e.g Request ID using an HTTP interceptor but for parameters that are 
> dependent on the current requests, I can't see any way to provide those in 
> requests.
> Look at this [NHS Summary Care Record FHIR API|
> https://digital.nhs.uk/developer/api-catalogue/summary-care-record-fhir#:~:text=to%20follow%20later.-,Overview,in%20the%20patient's%20direct%20care.]
>  it excepts a few extra parameters apart from ID.
> It requires these extra parameters :
> composition.identifier ( This is identifier of Bundle ID)
> composition.subject:Patient.identifier (The patient's NHS number. Must be 
> preceded with FHIR identifier 
> (eg."composition.subject:Patient.identifier=https://fhir.nhs.uk/Id/nhs-number|9000000009"))
> I don't see a way to provide these in FHIR Read Operations.  Maybe an 
> improvement can be done to extend ExtraParameters implementation to allow 
> custom parameters as well.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to