FHIR® and SMART on FHIR® Products
Data Quality in FHIR: Lessons from the Field
A presentation from HL7’s FHIR DevDays
Carol Graham, Clinical Architecture Product Manager, describes how implementers can close the gap between real-world use and the happy path use cases envisioned in interoperability standards, while complying with value set best practices, including HL7’s normative Value Set Definition standard. She addresses the importance of standardization and normalization on data quality within the FHIR resources.
Symedical® on FHIR™
Symedical® on FHIR™ is Clinical Architecture’s implementation of the HL7 FHIR Terminology Service specification. It provides a FHIR-based set of services customers may use to gain access to Clinical Architecture’s terminology and ontology assets. Customers may also use these services to provide access to their own content from within their own instance of Symedical, if desired. The functionality provides for code (term) lookups, validations, mappings to other code systems or value sets, determining hierarchical relationships between codes, and retrieving sets of codes and their descriptors. The FHIR Terminology service is based on commonly understood web standards: REST, XML, JSON, and HTTP.
FHIR Compatibility: R4, STU3 (R3), DSTU2
Pivot – Interoperability and data quality simplified
Pivot is an interoperability and data quality solution that combines format conversion, terminology normalization, de-duplication, and data validation into a single platform. Pivot takes in patient data in many formats (FHIR, CDA/C-CDA, HL7, and others), normalizes the data to the required code systems and value sets, validates the data, optionally performs de-duplication and other enhancements, and produces a standard, predictable patient message either in FHIR or any of the other available formats. It combines many of Symedical’s most powerful capabilities into a turnkey service, dramatically reducing the barriers and effort necessary to make high-quality patient information exchange a reality.
Unlike most interoperability platforms, which require custom interfaces for every message feed, Pivot is architected to isolate format transformations from normalization, validation, and other features, making it exceptionally easy to configure and integrate. It is stateless, reducing the cost and risk associated with duplicating patient data repositories, and it provides unparalleled flexibility and ease of implementation.
Pivot is suitable for use in a variety of settings and use cases, including IDNs/health systems, health information exchanges, analytics platforms, enterprise clinical data repositories, research settings, and more.
FHIR Compatibility: R4, STU3 (R3)