January 1, 2027 is closer than it looks. For payers, CMS-0057-F means five new or expanded FHIR APIs in production: Patient Access, Provider Access, Payer-to-Payer, Provider Directory, and Prior Authorization. That's not a single IT project. It touches UM workflows, provider operations, member data, and compliance reporting all at once. We put together the “CMS-0057-F strategic pack for payers” to help leadership teams cut through the noise and move faster. It brings together deep dives on each required API, a practical eBook connecting requirements to timelines, and expert perspectives on electronic prior authorization, in one place. If your team is still piecing together fragmented information, this is where to start. Link in the comments 👇 #CMS0057F #FHIR #Interoperability
Firely
IT-services en consultancy
Amsterdam, North Holland 4.040 volgers
Firely provides all the software, training and services you need to bring FHIR to life. We also run HL7 FHIR DevDays.
Over ons
Firely is a global digital healthcare company that provides all the software, training, and consultancy you need to bring FHIR to life. As one of the initiators of FHIR, Firely has been involved since the beginning and plays a prominent role in the evolution of the standard. Firely’s 100% FHIR-based solutions —Firely Server, Simplifier.net, and the official open-source .NET SDK for HL7 FHIR—are trusted by governments, hospitals, and health IT companies around the world to simplify compliance and interoperability. Dedicated to the worldwide adoption of FHIR, Firely takes a leading role in the FHIR community as a founding member of the FHIR Business Alliance and the driving force behind HL7 FHIR DevDays – the world’s foremost FHIR event.
- Website
-
http://fire.ly
Externe link voor Firely
- Branche
- IT-services en consultancy
- Bedrijfsgrootte
- 11 - 50 medewerkers
- Hoofdkantoor
- Amsterdam, North Holland
- Type
- Particuliere onderneming
- Opgericht
- 2015
- Specialismen
- FHIR Consultancy and Training, FHIR Software and Services, FHIR DevDays, Interoperability, FHIR, CMS compliance, ONC compliance, ISiK compliance, MedMij compliance, FHIR Server en Digital Quality Measures
Locaties
-
Primair
Routebeschrijving
Westerdok 442
Amsterdam, North Holland 1013 BH, NL
-
Routebeschrijving
228 E 45th St
Suite 9E
New York, NY 10017, US
Medewerkers van Firely
Updates
-
𝟭 𝗱𝗮𝘆 𝗹𝗲𝗳𝘁 𝘁𝗼 𝗿𝗲𝗴𝗶𝘀𝘁𝗲𝗿. If CMS-0057-F is on your roadmap, don't sit this one out. Deadlines aren't moving. And the teams that will be in the best position aren't the ones who moved fastest. They're the ones who got the architecture right before committing to platforms and timelines. On March 31, Michelle Beck is hosting three practitioners with hard-won experience from real CMS-0057-F implementations: Mathew Osmanski, Rakesh M., and Nate H.. They'll walk through the most common pitfalls, a realistic compliance roadmap through 2027, and the foundation that makes FHIR a long-term capability, not a one-time project. Bring your toughest CMS-0057-F questions. There's a live Q&A at the end. Reserve your seat! Link in the comments 👇 HIKE HEALTH® #FHIR #CMS0057F #Interoperability
-
-
New to FHIR and heading to DevDays in Minneapolis? This one's for you. Our FHIR Trainer Mirjam Baltus has written about why the HL7 FHIR Foundations Bootcamp was created, and it starts with something she's heard from hundreds of people: "I know I need to understand this better, but where do I begin?" The Bootcamp takes place on June 15, the day before the main conference. It's a practical, beginner-friendly introduction to the core building blocks of FHIR: resources, REST APIs, profiling, terminologies, and SMART on FHIR. Built for developers, architects, project managers, and clinical professionals alike. You'll learn through expert-led sessions and hands-on exercises, and wrap up the day with a Q&A featuring some of the biggest names in the FHIR community, including Grahame Grieve, James Agnew, Gino Canessa, and Firely's own Ewout Kramer. No prior FHIR experience required. Just curiosity. If you're coming to DevDays and want to arrive with context and confidence, read Mirjam's full post in the comments. Health Level Seven International #HL7 #FHIR #FHIRDevDays
-
-
Compliance gets you to the starting line. The organizations that will win on interoperability are the ones building for what comes next. Once you have a scalable FHIR infrastructure in place, the capabilities that open up go well beyond compliance: 🔹 Prior authorization automation — less manual work, faster decisions, better provider experience 🔹 Richer clinical data for risk adjustment and care management 🔹 Analytics readiness — consistent, structured data that actually supports reporting 🔹 Payer-to-payer exchange and reduced provider onboarding burden 🔹 A platform that absorbs new mandates without requiring you to rebuild None of this is automatic. It depends entirely on the architecture and design decisions you make during implementation. On March 31, Firely and HIKE HEALTH® are walking through what those decisions look like in practice, and how to make sure your CMS-0057-F program sets you up for what comes next, not just what’s required today. 🎤 Speakers: Michelle Beck, Mathew Osmanski, Rakesh M., Nate H. Register now 👉 https://lnkd.in/eMr6Hu_R #FHIR #CMS0057F #Interoperability #PriorAuth
-
-
CMS-0057-F doesn't have to be a cost center. For payers who get the architecture right, it becomes the foundation for something much more valuable: 📊 Near real-time dQM tracking and Stars/HEDIS performance gains 🏥 A longitudinal health record that powers care management and value-based care 👤 Better member experiences — fewer prior auth surprises, more personalized engagement 📉 A business case that shifts from "we had to do this" to "we're using this to compete" In part two of our guest blog series with HIKE HEALTH®, Nate H. makes the case for treating CMS-0057-F as a strategic investment, not just a compliance project. Read more https://lnkd.in/e8HzW8Qy #FHIR #CMS0057F #Interoperability
-
-
Firely heeft dit gerepost
𝗔𝗻𝗼𝘁𝗵𝗲𝗿 𝗦𝗶𝗺𝗽𝗹𝗶𝗳𝗶𝗲𝗿.𝗻𝗲𝘁 𝗿𝗲𝗹𝗲𝗮𝘀𝗲 𝗷𝘂𝘀𝘁 𝘄𝗲𝗻𝘁 𝗹𝗶𝘃𝗲 🚀 – 𝗳𝗼𝗰𝘂𝘀𝗲𝗱 𝗼𝗻 𝘀𝗲𝗰𝘂𝗿𝗶𝘁𝘆, 𝗺𝗲𝘁𝗮𝗱𝗮𝘁𝗮 𝗮𝗻𝗱 𝘂𝘀𝗮𝗯𝗶𝗹𝗶𝘁𝘆. We’ve rolled out a new Simplifier.net update that strengthens platform security while delivering powerful features for FHIR professionals. Let me tell you what’s new. 𝗠𝗲𝘁𝗮𝗱𝗮𝘁𝗮 𝗮𝘁 𝗮 𝗴𝗹𝗮𝗻𝗰𝗲 🧩 - The new {{𝚖𝚎𝚝𝚊𝚍𝚊𝚝𝚊}} widget lets you drop a full metadata table into your Implementation Guides. Use the default or pick your own fields (url, version, publisher, …) so every resource page shows consistent, up‑to‑date details without hand‑built tables. 𝗔𝗹𝗶𝗴𝗻 𝘆𝗼𝘂𝗿 𝗯𝗿𝗮𝗻𝗱 - The IG editor now supports custom preview images for your own 𝙲𝚂𝚂/𝙷𝚃𝙼𝙻 styles. Team members instantly see which look and feel matches which style in the picker. 𝗦𝘁𝗿𝗲𝗮𝗺𝗹𝗶𝗻𝗲𝗱 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 & 𝗰𝗹𝗲𝗮𝗿𝗲𝗿 𝗴𝘂𝗶𝗱𝗮𝗻𝗰𝗲 🧭 - The refreshed Learn page puts documentation, training and tools front and center as a single hub. And an updated “Not Found” page now hints when data might be private, reducing confusion when you’re not logged in. 𝗠𝗼𝗿𝗲 𝘀𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆 & 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 🛠 - From preserving style structures when copying guides to fixing STU3 rendering issues and improving 𝚐𝚞𝚒𝚍𝚎.𝚢𝚊𝚖𝚕 error messages, this release resolves dozens of bugs so your FHIR projects run more smoothly. As always, feedback drives our roadmap 💬 When you try these features, I’d love to hear what works for you – and what should come next. Full release notes: https://lnkd.in/dhtvrUiA
-
-
What does it actually take to implement CMS APIs for 1.8 million Medicaid members? Here's what to know. At HIMSS26, our Product Manager Alexander Zautke presented alongside Darlene Carr from the New Jersey Innovation Institute on implementing the CMS Patient Access and Provider Directory APIs for New Jersey's statewide Medicaid program. 1.8 million members. Five months from start to production. Here are five lessons from that experience that apply well beyond New Jersey: 1️⃣ 𝗜𝗱𝗲𝗻𝘁𝗶𝘁𝘆 𝗶𝘀 𝗵𝗮𝗿𝗱𝗲𝗿, 𝗮𝗻𝗱 𝗺𝗼𝗿𝗲 𝗰𝗿𝗶𝘁𝗶𝗰𝗮𝗹, 𝘁𝗵𝗮𝗻 𝗶𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲. The FHIR server is rarely where programs stall. Verifying who is requesting their data, at scale, without creating a barrier for elderly or disabled beneficiaries, is where the real work is. 2️⃣ 𝗬𝗼𝘂𝗿 𝗱𝗮𝘁𝗮 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 𝗯𝗲𝗰𝗼𝗺𝗲𝘀 𝘆𝗼𝘂𝗿 𝗔𝗣𝗜 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 𝗽𝗿𝗼𝗯𝗹𝗲𝗺. FHIR APIs don't create clean data. They expose whatever is already in your system. Understand your source data quality before you set your timeline, not halfway through. 3️⃣ 𝗔 𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝗲𝗻𝗱𝗽𝗼𝗶𝗻𝘁 𝗶𝘀𝗻'𝘁 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝗮𝘀 𝗮 𝘂𝘀𝗮𝗯𝗹𝗲 𝗼𝗻𝗲. Passing compliance checks means you meet the technical requirements. That's not the same as patients being able to rely on the API. Error rates, response times, and data freshness aren't compliance requirements, but they're what builds trust. 4️⃣ 𝗗𝗲𝗮𝗱𝗹𝗶𝗻𝗲 𝗽𝗿𝗲𝘀𝘀𝘂𝗿𝗲 𝗿𝗲𝘃𝗲𝗮𝗹𝘀 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂 𝗱𝗶𝗱𝗻'𝘁 𝗽𝗹𝗮𝗻 𝗳𝗼𝗿. The teams that handle this best are the ones who agree early on what truly needs to be live on day one, and what doesn't. 5️⃣ 𝗜𝗻𝘁𝗲𝗿𝗼𝗽𝗲𝗿𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗶𝘀 𝗲𝗰𝗼𝘀𝘆𝘀𝘁𝗲𝗺 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗔𝗣𝗜 𝗮𝘃𝗮𝗶𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆. An endpoint without a developer portal, app vetting, and admin controls isn't really interoperability. It's a prerequisite. Read the full blog in the comments 👇 #FHIR #CMS0057F #Interoperability #HIMSS26
-
-
"The community is really nice and welcoming, and the tutorials have been really informative. Something I can definitely bring home to my own workplace and use in the future." That's what a first-time attendee said after DevDays 2025. Whether you're new to FHIR or deep in an implementation, DevDays is where you find your people and leave with practical skills from hands-on tutorials, strategic conversations, and hallway chats that turn into real collaborations. See for yourself in the video below! We're heading back to Minneapolis this June, and early bird pricing is now open. Registration link in the comments 👇 Health Level Seven International #HL7 #FHIRDevDays #FHIR
-
Month 1–2: Platform selected ✅ Month 3–4: APIs deployed ✅ Month 5–6: Identity mismatches, consent gaps & terminology issues ❌ Month 10+: Program resets. This pattern shows up across CMS-0057-F implementations more than it should. It's not a technology failure — it's an architecture failure. We're fortunate to have our friend Nate H., CISO at HIKE HEALTH®, weigh in. He breaks down exactly why it happens, what the hidden operational work actually looks like, and the architecture questions your team should be asking before committing to platforms and timelines. If your organization is planning or already mid-implementation, this is the architecture conversation worth having now. Read it here 👉 https://lnkd.in/efgezW57 #CMS0057F #FHIR #Interoperability
-
-
Last year, 54% of national FHIR experts expected strong growth in FHIR adoption in the coming years. Is that playing out in your country? Have your say in the 2026 State of FHIR Survey. If you're a national expert or implementer, get in touch with Ward Weistra. Especially if your country wasn't part of last year's 59! #HL7 #FHIR #StateOfFHIR
Last year, experts from 𝟱𝟵 𝗰𝗼𝘂𝗻𝘁𝗿𝗶𝗲𝘀 gave us the most comprehensive picture as to where FHIR is progressing around the world. This month we’ve launched the 𝟮𝟬𝟮𝟲 𝗲𝗱𝗶𝘁𝗶𝗼𝗻 of the 𝗦𝘁𝗮𝘁𝗲 𝗼𝗳 𝗙𝗛𝗜𝗥 𝗦𝘂𝗿𝘃𝗲𝘆. It is our fourth annual effort to capture insights into adoption, implementation and the challenges countries face to scale interoperability. This year we’re again asking national experts and implementers to share: ■ Where FHIR is being used in production ■ Which versions and specifications are gaining traction ■ What’s driving adoption — and what’s holding it back 𝗡𝗲𝘄 𝘁𝗼𝗽𝗶𝗰𝘀 include the FHIR Community Process (FCP) and AI impact on health data exchange. The results will again be presented in June at the 𝗛𝗟𝟳 𝗙𝗛𝗜𝗥 𝗗𝗲𝘃𝗗𝗮𝘆𝘀 𝟮𝟬𝟮𝟲 in Minneapolis. If you receive an invitation, I hope you’ll consider contributing. This survey only works because of the community’s willingness to share experiences. And if you know colleagues who should be represented, feel free to point them our way. Let’s continue building a clear view of where FHIR stands — and where it needs to go next 👊 #FHIR #StateofFHIR
-