Support Returning Response Headers from FHIR Calls for Errors

[MichaelLeeHobbs]

Expected Behavior

await client.search({resourceType, searchParams}) throws and should be able to call const { response, request } = Client.httpFor(err) to get the response.

Actual Behavior

response is undefined

Steps to Reproduce the Problem

        it('should search for Patient resources for zztest', async () => {
            try {
                const patients = await client.search({resourceType: 'Patient', searchParams: {family: 'zztest'}});
                console.log(patients);
                expect(patients).toBeDefined();
                expect(patients.resourceType).toBe('Bundle');
                expect(patients.entry.length).toBeGreaterThan(0);
            } catch (err) {
                console.error(JSON.stringify(err, null, 2));

                const { response, request } = Client.httpFor(err);
                console.log(response); // <======= undefined
                throw err;
            }
        }, 10000);

Specifications

• Version: ^1.9.2
• Platform: node v18.17.0
• Subsystem: ? not sure what this is looking for

As a workaround I just added console.log('response.headers', headers); to line 173 of http-client.js. This is not a feature we normally need but Cerner is sending 422 and they needed the X-Request-Id to troubleshoot their side.

[bkaney]

Okay, we will look into this thanks for the issue!