Stream: implementers
Topic: will we be compliant to some level
mabedi motimedi (Feb 22 2018 at 07:43):
hello everyone i am new to HL7- FHIR and will like advice and clarity ,my limited understanding is this:
we are wanting to integrate with other systems, and expose the data we have in our database we have patients, users, medical history, prescriptions,
we build a broker to follow the resource type provided
once we have written end points that expose these and the FHIR test server confirms they are correct, then we have reached the level of compliance? thank you
Grahame Grieve (Feb 22 2018 at 07:48):
that's the best amount of testing we have now
mabedi motimedi (Feb 22 2018 at 07:53):
that's the best amount of testing we have now
thank you other than the FHIR HAPI server for testing what tool do you also recommend that may help in HL7 compliance testing ?
Ewout Kramer (Feb 22 2018 at 09:44):
that's the best amount of testing we have now
thank you other than the FHIR HAPI server for testing what tool do you also recommend that may help in HL7 compliance testing ?
You could test against other servers (http://wiki.hl7.org/index.php?title=Publicly_Available_FHIR_Servers_for_testing) (for the client parts), and use TouchStone or Crucible to validate your FHIR endpoint.
Richard Ettema (Feb 22 2018 at 12:42):
You can find links to Touchstone and Crucible here: http://wiki.hl7.org/index.php?title=FHIR_Testing_Platforms
mabedi motimedi (Feb 22 2018 at 13:53):
You can find links to Touchstone and Crucible here: http://wiki.hl7.org/index.php?title=FHIR_Testing_Platforms
thank you much appreciated
mabedi motimedi (Feb 22 2018 at 13:54):
that's the best amount of testing we have now
thank you other than the FHIR HAPI server for testing what tool do you also recommend that may help in HL7 compliance testing ?
You could test against other servers (http://wiki.hl7.org/index.php?title=Publicly_Available_FHIR_Servers_for_testing) (for the client parts), and use TouchStone or Crucible to validate your FHIR endpoint.
thank you much appreciated
Lloyd McKenzie (Feb 22 2018 at 15:39):
Keep in mind that the "base" FHIR standard only defines a limited degree of interoperability. It doesn't require all systems to support all elements, nor does it nail down what code systems are to be used. Some jurisdictions have defined implementation guides (e.g. US-core, Australian-core) that set tigher constraints for interoperability in those jurisdictions. Conformance testing is more meaningful when done against such implementation-environment-specific guides
Peter Jordan (Feb 22 2018 at 19:39):
My expectation is that all FHIR servers should be able to produce a Capability Statement that complies with the relevant version of FHIR, and comply with all the capabilities declared in that statement.
Lloyd McKenzie (Feb 22 2018 at 20:50):
Sure - but compliant with the FHIR base spec doesn't mean interoperable or useful. You'll generally want more than just that.
Peter Jordan (Feb 22 2018 at 20:54):
Agreed - but compliance with the base spec is critical and my fear is that many won't get that far - particularly those who choose not to use the Reference Libraries or Server Templates such as HAPI or Vonk.
Last updated: Apr 12 2022 at 19:14 UTC
