Is FHIR at the center of your organization’s data sharing strategy?
Are you a product owner tasked with delivering a project that uses FHIR?
Here are five posts I wrote over the past year for business stakeholders and leaders.
I talk about FHIR decisions they need to be aware of, mistakes that many teams make when it comes to FHIR, and what they should know about the future of FHIR.
- The five experts your FHIR project needs
A team of developers is not enough. Have you got medical expertise, terminology expertise and legal and compliance expertise on your team?
https://darrendevitt.com/the-5-experts-your-fhir-project-needs/ - The pros and cons of using a managed FHIR server
AWS, Google Cloud, Azure Health Data Services — are you making the right decision in handing over responsibility for managing your FHIR data to another company?
https://darrendevitt.com/the-pros-and-cons-of-using-a-managed-fhir-server/ - FHIR maturity levels — how exposed are you?
Is you solution using FHIR resources or elements that will be deprecated in R5 or R6? Are you creating a headache for the future?
https://darrendevitt.com/fhir-maturity-levels-how-exposed-are-you/ - Seven FHIR decisions your devs should not make
Many FHIR decisions are not technical. You need to know what those decisions are and not allow your developers to make them.
https://darrendevitt.com/organizations-new-to-fhir-often-assume-all-fhir-decisions-are-technical/ - The future roadmap of FHIR
What’s coming down the tracks for FHIR? What does the future hold and what does that mean for your project?
https://darrendevitt.com/the-future-roadmap-of-fhir/
---