FHIR Chat · R4B testing · Touchstone

Stream: Touchstone

Topic: R4B testing


view this post on Zulip Lee Surprenant (Jan 12 2022 at 13:41):

Are there any plans for a FHIR 4.3.0 test suite?

view this post on Zulip Wendy Gereke (Jan 12 2022 at 13:59):

Hi @Lee Surprenant , Thanks for the outreach! We do not typically build conformance suites for snapshot releases of FHIR. Is there a specific test result you'd like to be able to publish? With some additional context around why you are inquiring about test suite plans for FHIR 4.3.0 we can provide additional support.
Thanks,
Wendy

view this post on Zulip Lee Surprenant (Jan 12 2022 at 14:04):

Hi Wendy, I'm "at" connectathon and one thing I like about this event is we get access to touchstone tests. One of my goals for this connectathon was to kick the tires on my 4.3.0 implementation (to validate our implementation and also the spec--hopefully finding any spec issues before it gets published). I'm able to target our impl with the 4-0-1 test suite and will probably start that soon, but not sure if it will complain or not (e.g. my CapabilityStatement won't be valid per the 4.0.1 spec)

view this post on Zulip Lee Surprenant (Jan 12 2022 at 14:05):

Another reason I asked is because I'm trying to gauge the community interest in moving to 4.3.0 and I think having a test suite available for that version could help in this regard.

view this post on Zulip Lee Surprenant (Jan 12 2022 at 14:06):

Its mostly the same as 4.0.1, so I was curious if aegis would just rename the suites (the same way they went from 4.0.0 to 4.0.1) or if it would be a separate suite

view this post on Zulip Wendy Gereke (Jan 12 2022 at 14:39):

Thanks Lee! I apologize for my askew answer - we will be offering testscript support for FHIR 4.3.0. I do not have a timeline for that at this time but we will keep the community updated.

view this post on Zulip Lee Surprenant (Jan 12 2022 at 16:08):

FYI, as expected we're failing the touchstone basic tests due to our CapabilityStatement

The rule 'AssertResponseCodeIfSupported.groovy' ('assertResponseCodeOkIfVersioning' in this execution) produced the error: Could not find "The expression "(CapabilityStatement.rest.where(mode = 'server').resource.where(type = 'Account').where(versioning = 'versioned' or versioning = 'versioned-update').exists())" is invalid. Message: "Evaluate To Boolean exception evaluating fhirpath expression [(CapabilityStatement.rest.where(mode = 'server').resource.where(type = 'Account').where(versioning = 'versioned' or versioning = 'versioned-update').exists())]. Unknown FHIRVersion code '4.3.0-CIBUILD'.".".


Last updated: Apr 12 2022 at 19:14 UTC