FHIR Chat · Capability Statement Tests

Stream: Touchstone

Topic: Capability Statement Tests - C15

Peter Jordan (Apr 19 2017 at 05:01):

@Richard Ettema I'm now struggling with the Capability Statement Tests - they seem to assume that a server implements Patient Resources. I'm also not sure why an ETag header is required when my server does not support versioning for any resources. Any help welcome.

Richard Ettema (Apr 19 2017 at 19:16):

@Peter Jordan Thanks. I created an AEGIS internal Touchstone JIRA tracking ticket for this issue (TS-318) and corrected the resource type to now be CapabilityStatement. This correction has been uploaded to the Touchstone production environment.

Richard Ettema (Apr 19 2017 at 19:18):

You'll need to modify your CapabilityStatement to include the CapabilityStatement resource type with the versioning setting for 'no-version' as follows:

         "resource":[
            {
               "type":"CapabilityStatement",
               "versioning":"no-version",
               "readHistory":false,
               "updateCreate":false
            },
         ...

Peter Jordan (Apr 20 2017 at 22:52):

Thanks, @Richard Ettema . I had a feeling that I might need to do something like that, but hadn't seen it in any example CS. Updated my server and it's now out of the red.

Peter Jordan (Apr 21 2017 at 20:47):

Thanks @Richard Ettema. Was wondering if I had to add that resource type; hadn't seen that in any examples but it's done the trick and I'm out of the red once more.

Last updated: Apr 12 2022 at 19:14 UTC

Main menu