Built around the visionary HL7 FHIR standard and powered by HAPI, the most proven FHIR implementation in the world.
We have authorization, audit, compliance monitoring tools, and security integration built-in. It’s privacy by design.
Your data strategy should be as unique as your business. We can help build a configuration that works for you.
Out-of-the-box, enterprise-level capabilities so developers can get started immediately. Build faster than ever before.
Smile CDR is a complete, purpose-built clinical data repository designed around the HL7 FHIR standard that is used for storing health records.
Smile CDR is powered by HAPI FHIR , the open-source reference implementation of the FHIR standard. With Smile CDR, HAPI users globally have the option to seamlessly transition from an unsupported open source FHIR server to a commercially supported, enterprise class FHIR repository when ready.
By using Smile CDR, organizations can enable interoperability of their health systems using a standards based product that leverages the most proven FHIR implementation in the world.
Smile CDR is designed to help your developers meet their project targets and build exciting new solutions on top of FHIR. It takes all of the data work out of their way and provides them with a modern, REST-ful service interface with rich query capabilities. As it uses Web services in an intuitive way, you can hire developers with current skills and put them to work building your applications, faster than with older and more challenging standards.
Smile CDR has a built in terminology server, which can be used as a structural element of queries. The terminology server can be used to load Snomed CT, ICD 9, ICD 10, LOINC and other standards or be extended to map to local coding systems. By leveraging the terminology server, queries can be constrained by named element directly through search parameters. This can be very exible, especially when used in conjunction with full text indexing.
Smile CDR supports notication based on matching rules for data. With this capability it is possible to send a notification if a particular message or value is received by the CDR. This is helpful when the CDR is part of a record processing ecosystem. For example, inbound ADT messages could trigger an update to the Patient Index solution.
Smile CDR comes with a suite of management tools that included performance visualization, module conguration, audit records and much more. The management server is designed to inform administrators of the status of the services in a way that is both easily consumed and highly informative.
Smile CDR stores clinical data in your choice of relational databases such as Oracle and Postgres. In addition, it uses Apache Lucene to keep indexed search fields for text elements. The solution is highly scalable, supporting many parallel systems in a clustered conguration. Smile CDR is only constrained by the capacity of the underlying database technology. So the solution can store billions of records, with full text indexing.
Smile CDR uses the Apache Lucene search library to index text fields. This feature is associated with the standard FHIR query capabilities, enabling fast resolution of text data, such as name or description. The solution is designed to support type-ahead searching and responds with suggestions to character strings. This functionality is particularly powerful when used as part of a search helper function in which the full string has not yet been supplied.
Smile CDR is configurable as a multi-node redundant solution. Every transaction is stateless, so nodes can be added and removed as required without loss to the transaction ow. In this way, it is possible to leverage some of the advantages of cloud services when scaling up and down to meet capacity demands.
Smile CDR can be configured and installed in minutes. The installation requires a database for data storage and a location to run from. There needs to be enough disk to support the Lucene indexes, however, the majority of the data resides in a centralized database cluster. Simply copy the executables to a permanent home, configure the target database and local passwords and then run the solution.
Any organization who needs to store health records in a secure compliant way, while wishing to easily access those records using standards-based APIs will greatly benefit from using a FHIR repository. It's built for business.