Sold by
Smile Health Data Platform | FHIR® Interoperability
FHIR native platform to ingest, normalize, store, and share health data with APIs, consent, MDM, CQI
The Smile Health Data Platform is a configurable, FHIR-first platform that integrates with existing cloud infrastructure, software, and healthcare compliance and performance monitoring workflows. It serves as an innovation accelerator with event-driven capabilities (FHIR Subscriptions), clinical reasoning for real-time care-gap analysis, and a composable architecture.
Reviews (3)
reviewer2879100
Trusted data standardization has supported national-scale analytics and drives accurate decisions
Reviewed on Jul 23, 2026
Review from a verified AWS customer
What is our primary use case?
My primary use case is Smile Digital Health’s Omni platform for standards-based processing of healthcare data using FHIR. We use its FHIR-based capabilities to transform disparate healthcare data into trusted golden records. Smile’s HL7-aligned methods provide a consistent and professionally governed approach to interoperability and data quality.
How has it helped my organization?
Smile Digital Health has positively impacted our organization by providing proven, standards-based FHIR processes that improve consistency, transparency, and confidence in our data. Its established methods reduce uncertainty about how healthcare information is transformed, validated, and exchanged.
What is most valuable?
Smile Digital Health’s strongest features include its Omni health data platform, FHIR-native interoperability capabilities, terminology services, validation tools, and high-volume processing capacity. Omni can process up to 250,000 transactions per second, on modest infrastructure and configuration, making it well suited for large-scale healthcare data environments.
Its performance and scalability reduce the risk that the interoperability platform will become a processing bottleneck. Smile also applies FHIR, HL7 implementation guides, CQL, CDS Hooks, and SMART on FHIR to support consistent data exchange and computable healthcare workflows. This combination of technical performance and standards expertise allows us to trust both the process and its outcomes.
What needs improvement?
Smile Digital Health’s offerings are mature and reliable. Continued investment in implementation accelerators, expanded preconfigured mappings, automated validation, and user-friendly configuration tools could make deployment even faster for organizations with complex data environments.
For how long have I used the solution?
I have been using Smile Digital Health for several years.
What do I think about the stability of the solution?
Smile Digital Health is stable, effectively managing the health IT infrastructure for countries.
What do I think about the scalability of the solution?
Smile Digital Health’s scalability is impressive. Its Omni platform can process 250,000 transactions per second, on modest hardware. Additional infrastructure can further expand its capacity, making the platform suitable for large and growing healthcare data environments.
How are customer service and support?
Customer support from Smile Digital Health is great. My emails are typically answered within 30 minutes to an hour, often within 10 minutes.
I rate customer support highly because they are very cordial and provide customer manager, which helps prioritize requests and ensure smooth resolutions.
Which solution did I use previously and why did I switch?
Before choosing Smile Digital Health, I evaluated other approaches. However, Smile stood out because of its FHIR expertise, standards-based architecture, scalability, and established healthcare interoperability capabilities.
How was the initial setup?
The initial setup was very straightforward, particularly with the training and implementation support available through Smile’s technical partner program.
What about the implementation team?
We did not use an external integrator or reseller. Tetra Fields is a Smile Digital Health Technical Partner, which allows us to work directly with Smile and purchase its technology without using the AWS Marketplace.
What was our ROI?
I have seen a return on investment because Smile provides trusted capabilities grounded in widely adopted healthcare standards. Its technology reduces the time and uncertainty associated with building interoperability functions from the ground up. For example, HAPI FHIR is open source and widely adopted, demonstrating Smile’s commitment to accessible, reusable, and high-quality interoperability technology.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for Smile Digital Health is that they are very reasonable, with the partner training making the implementation and setup a turnkey process.
Which other solutions did I evaluate?
I evaluated other healthcare interoperability approaches, but none offered the same combination of FHIR maturity, scalability, standards expertise, and implementation support. Smile has supported large national and enterprise healthcare data environments, including deployments in Canada and Australia, as well as major payer and provider organizations.
What other advice do I have?
Smile Digital Health is a proven and reliable platform. Its ability to support national-scale healthcare interoperability demonstrates the maturity of its technology and standards-based processes. Organizations seeking a scalable health data and interoperability backbone should strongly consider Smile Digital Health. I rate the platform 10 out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Alex Lorenzo
FHIR repository has streamlined patient registration and preserved accurate unified records
Reviewed on Jul 03, 2026
Review from a verified AWS customer
What is our primary use case?
Smile Digital Health was used as a backend clinical data repository for storing patient data, patient-related data, and patient-related questionnaires. Patient registration was a primary use case for how Smile Digital Health was utilized. Several questionnaires that patients had to fill out were stored in the clinical data repository. Smile Digital Health was primarily used as a way to remain FHIR compliant. In the past, we were attempting to do integrations with a healthcare exchange network, and that required us to exchange FHIR.
Initially, when we were planning on doing the healthcare exchange piece, there was a feature provided that allowed us to maintain a golden patient record, which stands out the most. If a new record was exchanged over the healthcare exchange network, we could ensure that we weren't duplicating patient resources or patient objects on the backend. Outside of the CDR, that was what was primarily used.
What is most valuable?
Features were completed quicker as the team developed familiarity with how objects are structured within the clinical data repository on Smile or the CDR side of Smile, which made feature development much faster. There was the addition of some complexity when objects needed to be modified or research had to be conducted, but this was resolved as the team gained experience. Outside of the CDR, other features could have been utilized and implemented, but the CDR was the primary focus.
What needs improvement?
Since I no longer work with the product, I cannot specify how Smile Digital Health can be improved. Too little of the feature set was used to provide good commentary regarding any needed improvements for Smile Digital Health. There are no improvements that come to mind regarding Smile Digital Health that have not been mentioned yet.
For how long have I used the solution?
I have used Smile Digital Health for over four years.
What do I think about the stability of the solution?
There are no stability issues at the moment.
What do I think about the scalability of the solution?
There are no scalability issues that come to mind. The clinical data repository was the only component needed.
How are customer service and support?
The team was very quick to respond to issues that we had with the product, even when there were issues created by us when we were utilizing the product. They were easy to contact, and it was easy to create tickets. The response time was within hours, sometimes within the day. Overall, it was a great experience dealing with their account management team, technical support staff, and architects.
What other advice do I have?
If you are a small or medium-sized company that needs a clinical data repository, Smile Digital Health is definitely the cheaper alternative for those looking into using a clinical data repository. Smile Digital Health is FHIR compliant and is compliant up to the latest standard of FHIR. I did not get a chance to work with the AI stack regarding Smile Digital Health's accuracy and reliability of output. The only features utilized were the CDR and one particular feature for ensuring consistency with records.
I would rate this product a 10 overall.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
EricKim
Structured FHIR workflows have enabled me to focus on interoperability and business logic
Reviewed on Jun 30, 2026
Review provided by PeerSpot
What is our primary use case?
I have been working at my current company since June of 2022, and I also had a software engineer internship back in 2021, which is when I first started as a software engineer.
I have been using Smile Digital Health at my current company since I started back in 2022, specifically with multiple repositories we have, mainly Java ones that we use for interoperability.
My main use case for Smile Digital Health is through FHIR interoperability, as my team uses it as part of the infrastructure for exchanging and processing FHIR resources between different healthcare systems. One specific example that comes to mind is a prior authorization integration project where I worked on the API routing, building that on the Java side, and creating the transformation logic for the FHIR payloads, moving that between the provider and payer system. I was not necessarily developing Smile Digital Health itself, but I worked with it regularly as part of the API routing and data transformation.
Overall, I had a pretty good experience working with Smile Digital Health during that prior authorization integration project. One thing that stood out was that it handled a lot of the FHIR-specific complexity, allowing me to focus more on the actual business logic since the entire point of FHIR is to standardize everything. I could focus on the integration requirements instead of reinventing a bunch of healthcare-specific functionality myself. The other thing that stood out to me was just how strict healthcare interoperability can be, as a tiny issue with the profile or resource structure could cause problems downstream. Having the tool built around the FHIR standards was definitely helpful for troubleshooting and validation.
One thing that surprised me about my main use case and experience working with Smile Digital Health is that it is less about writing complicated code and more about ensuring every party, such as a payer system and a provider system, interprets the same standard, which is FHIR. Even when two systems are compliant with FHIR, differences in profiles or required fields can still arise. That was definitely surprising. Working with Smile Digital Health gave me a better appreciation for that aspect of interoperability, highlighting why validation conformance testing is such a significant part of healthcare projects. There is a lot that I took away, not just technically but also in understanding my professional development.
What is most valuable?
From my perspective, the best features Smile Digital Health offers include out-of-the-box support for FHIR. Not having to build any infrastructure ourselves saves a lot of time. The validation capabilities are especially useful when working with Implementation Guides and ensuring resources conform to the expected profiles and requirements. More generally, having a platform that understands interoperability standards specifically in healthcare smooths out integration work compared to trying to stitch together generic tools.
One example of how the validation capabilities helped my team was when we integrated with external systems that each had their own implementation requirements on top of the defined FHIR standard. We occasionally ran into issues where a payload was technically valid JSON and looked fine at first glance but was ultimately missing a required field or was not conforming to the expected profile. Having the validation tooling catch those issues saved us a lot of unnecessary debugging and helped identify potential failures downstream much earlier in the process, allowing us to fix them before they left our side.
One thing I appreciated about the features of Smile Digital Health is that it helped us concentrate on the integration and business logic side instead of spending time rebuilding healthcare-specific infrastructure ourselves. I came away with an appreciation for how much work these platforms save you when dealing with real-world interoperability challenges, simplifying everything.
From what I saw, the positive impact of Smile Digital Health on my organization is that it reduced the amount of custom infrastructure we had to build. Since many of the FHIR capabilities were in place, my team could spend more time on the actual integration requirements and the business logic that makes up the entire project. I think it also improved collaboration, as everyone works against the same standards and FHIR data models; a lot of time can get lost in healthcare projects in terms of how systems should communicate. Having a common FHIR standard made those conversations and integrations smoother, ultimately shortening the project timeline in building everything instead of starting from scratch.
What needs improvement?
In terms of improvements for Smile Digital Health, there was not anything major that stood out as broken or missing for my use case or the company's needs. Most of what we required was handled well. If I had to nitpick, I would say sometimes the learning curve and visibility into what is happening under the hood could be tricky, especially when debugging across multiple systems. A bit more straightforward observability or clearer error messaging would have made troubleshooting faster. However, I did not find anything that prevented us from accomplishing our tasks, and I was very satisfied.
If I had to add something about needed improvements, it would relate to documentation. The platform itself is solid, but when working across multiple systems, it was not always obvious where an issue originated—whether it was from our Java services, an external system, or how Smile Digital Health interpreted a FHIR resource. Clearer guided troubleshooting or examples in the documentation could have helped with those edge cases. However, integration-wise, it worked fine for what we needed; during tricky moments, I sometimes had to dig deeper to understand where and what went wrong.
For how long have I used the solution?
I have been working at my current company since June of 2022, and I also had a software engineer internship back in 2021, which is when I first started as a software engineer.
What do I think about the stability of the solution?
From my experience, Smile Digital Health is generally quite stable with no significant downtime issues. Most of the problems I encountered were related to integration or data payload mismatches instead of the platform being unstable. Overall, I would say it is pretty stable based on how I have worked with it.
What do I think about the scalability of the solution?
Regarding scalability, I did not personally work on performance testing or formal metrics, but from my perspective on the integration side, it handled the volume of FHIR transactions we managed without issue. Adding more integrations or resource types did not result in noticeable performance bottlenecks for the platform itself; most scaling challenges came from our services or how we structured the APIs around it. I found it quite capable within the scope we utilized.
How are customer service and support?
I had no interaction with Smile Digital Health's customer support, so I cannot speak to that. Any issues we faced were resolved internally or through our integration efforts, which reflects the stability of the tool itself, as we never needed to contact support.
Which solution did I use previously and why did I switch?
I was not part of the decision to adopt Smile Digital Health and am unaware of what solution the team was using before or if there was a one-to-one replacement. Smile Digital Health was already in place when I joined, and my focus has been on contributing to existing integration efforts.
What was our ROI?
Personally, as a software engineer, I have not observed a return on investment or any formal metrics regarding savings or time saved. My involvement has been strictly on the implementation and integration side, which does not include tracking that information.
What's my experience with pricing, setup cost, and licensing?
I cannot comment on pricing, setup cost, or licensing for Smile Digital Health because, as a software engineer, I was not engaged in that area. I lack visibility into any associated costs or structures.
What other advice do I have?
Regarding Smile Digital Health's AI capabilities, I cannot comment on their internal governance and security because I was not involved directly with those parts of the platform. However, from my observations of working on the integration piece, it aligns with typical healthcare patient system requirements. It handles sensitive data and implements role-based access consistent with HIPAA regulations in our operational environment. I cannot elaborate on the AI governance layer beyond that, as I have no direct experience.
As I mentioned earlier, I did not work with the AI capabilities of Smile Digital Health, so I cannot speak to the accuracy or reliability of any AI-generated outputs relating to record screening. My exposure mainly centers around FHIR integration on the Java services side, without evaluating AI features.
I was not involved in the infrastructure deployment side directly, so I cannot detail the exact setup. What I can say is that it is part of a healthcare integration ecosystem where deployment is managed in a controlled environment consistent with hospital requirements. It was not treated as a purely public system-as-a-service tenancy; rather, it was integrated into a managed setup with security and compliance as significant considerations. I did not take part in the actual deployment or on-premises decisions, so I cannot provide further details.
My team did not track formal metrics for efficiency gains, but there were clear practical improvements. The biggest one was the reduction of iteration time; previously, cycles slowed down due to malformed FHIR payloads or resources missing required fields. With the validation and standardized structure in place, we could catch those issues earlier, resulting in less time spent on back-and-forth debugging. This also made onboarding new integrations smoother because we were building within an established FHIR framework instead of reinventing the wheel for every project. Although we did not quantify it formally, the development and testing cycles were definitely less painful and more predictable for every iteration, which is huge.
My advice for others considering using Smile Digital Health is to start with a solid understanding of FHIR and your integration patterns. The platform works best when you have a clear idea of your data models and the workflows you want to support. Based on my experience, success relies more on how well your systems align on implementation details than on the tool itself.
My experience has mainly focused on the integration side, particularly involving anything FHIR-related. The main takeaway for me is the significant value derived from having a structured healthcare data layer in place, which reduces the information validation challenges and all the interoperability complexities, allowing me to focus strictly on the actual integration logic itself.
I would rate my overall experience with Smile Digital Health an eight out of ten.