Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement a private FHIR validator https://www.hl7.org/fhir/validation.html #21

Open
JRPearson500 opened this issue Dec 30, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@JRPearson500
Copy link
Member

Validating the FHIR health record that is generated by the Alpha data model can currently be done in two ways.

Offline - using a python library called fhir.resources - https://github.com/nazrulworld/fhir.resources:

  • Pros: it is fast
  • Cons:
    o It is not clear how fast the library keeps up with new FHIR standards
    o Seems to not be rigorous enough - we have found examples that pass offline validation checks but fail online
  • Online - by connecting to the HAPI FHIR server - https://hapifhir.io/:
  • Pros: listed as an official FHIR test server (https://wiki.hl7.org/Publicly_Available_FHIR_Servers_for_testing), so we expect
    it is kept up to date with current FHIR standards
  • Cons: it is slow

To combine the best of both worlds, namely, a fast validator that keeps up to date with changing FHIR standards, we recommend
implementing a private FHIR validation server in the future. This could have the added benefit of building a custom version that, for
instance, validates FHIR data that is also compliant with PRSB core information standards.

We would recommend implementing validation at the point when the config is being read, and when an output is generated. This will protect against an invalid entry / output being generated.

@JRPearson500 JRPearson500 added the enhancement New feature or request label Dec 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant