Reminder: Do not include any PHI or PII in Confluence. If you require 508 accessibility assistance or any other support for this system, then please send an email to onc-jira-questions@healthit.gov
| Barrier | Why is this a barrier? | Existing Industry Solutions? |
1 | Requirements | Core Capabilities are still in the process of being defined. In order to establish testing and certification of FHIR at Scale, we must document clear requirements in a format that provides clear understanding of how to accomplish “success”. | FHIR Implementation Guide Process |
2 | Contingencies | Testing and Certification of FHIR at Scale depends on baseline FHIR Conformance as well as integration of barriers to applicable FHIR Implementation Guides. | FHIR Validation Engine Da Vinci Implementation Guides |
3 | Tooling | FHIR implementation is a complex process that requires validation of several layers. Development of FHIR is often done with independently written tests. Often these tests do not include validation of base FHIR resources or do not establish adequate validation. Independent validation through automated tooling ensures a higher level of conformance. | Inferno Crucible Touchstone |
4 | Versioning | Change is inevitable. A successful testing and certification program will require processes and tooling that are nimble enough to handle a continuous cycle of updates to the FHIR specification. | |
5 | Timing | Testing of FHIR clients and servers should happen early and often. Encouraging use of FAST Core Competency Requirements as systems are being built (test driven development) will empower rapid success. | |