Why FCP compliance matters (and how Simplifier helps you get there)

When we talk about interoperability, most of us think about FHIR: the open, flexible standard that connects systems, data, and people across healthcare. But as the community grows, so does the challenge: how do we make sure that all those Implementation Guides (IGs) and specifications meet the same level of quality and transparency?

That’s exactly why HL7 International introduced the FHIR Community Process (FCP).

The FCP is more than just another framework or checklist. It’s a shared commitment within the global FHIR community to raise the bar on quality, documentation, and collaboration. It defines how organizations publish, validate, and maintain their FHIR specifications — ensuring they can be trusted, reused, and adopted across borders.

And, yes, if you get it right, you even earn the official FCP sticker — a seal of approval that signals to the world: this Implementation Guide follows the highest HL7 standards.

Why FCP compliance Matters

FHIR’s greatest strength — its openness — is also its biggest challenge. Anyone can publish an Implementation Guide, but that freedom sometimes leads to inconsistency in structure, documentation, or validation.

FCP compliance helps solve that by enforcing a few key principles:

• Transparency — Clear documentation of who’s involved, how feedback is processed, and how decisions are made.
• Quality assurance — Each IG must pass the official HL7 IG Publisher validation with zero errors.
• Community involvement — Public issue tracking, version control, and visibility into how issues are resolved.

When you follow this process, you’re not just producing another specification — you’re creating something that others can trust, reuse, and build upon. It’s the difference between a local project and a recognized global standard.

For national authorities, accelerators, or vendors, that translates into faster adoption, lower maintenance costs, and fewer disputes down the line.

The challenges on the road to compliance

Of course, getting there isn’t simple.

Many organizations start out enthusiastic about joining the FCP, only to realize that compliance isn’t just about code — it’s about governance and consistency.

• You need a documented FCP compliance policy explaining how your organization manages licensing, IP, decision-making, and transparency.
• You need to track and resolve issues publicly, with an audit trail of feedback, responses, and outcomes.
• You need to publish your Implementation Guide according to HL7’s technical rules — with versioning, dependencies, and metadata structured correctly.
• And finally, you need to validate it all through the IG Publisher, with zero errors before your guide can earn the FCP seal.

That’s a lot to manage… especially when your goal is to deliver real-world impact, not just paperwork.

How Simplifier helps you get there

This is where Simplifier.net, as a FHIR collaboration platform, makes the difference.

The platform helps you operationalize FCP compliance by embedding governance, validation, and documentation directly into the way you work. You can:

• Document your processes — Store and maintain your FCP compliance policy, license details, and project metadata in one structured space.
• Manage community feedback — Use Simplifier’s built-in issue tracker to log, categorize, and resolve public feedback. You can even create custom status flows (e.g., New → In Review → Resolved) that reflect your governance process.
• Validate your Implementation Guide — Run the official HL7 IG Publisher inside Simplifier’s Quality Control module. The system automatically identifies errors, links them to specific files, and helps you achieve that crucial zero-error result.
• Track and prove quality — Keep human and machine-generated issues side by side for a full audit trail of your development and review process.

Once you’ve done all that, you’ll not only have a stronger IG, you’ll have the documentation and evidence to show you’re truly FCP-compliant.

And that’s when you can proudly display that FCP sticker 😀 — a small symbol with big meaning: your work meets the global benchmark for quality and transparency in FHIR.

What’s the bigger picture?

Beware: FCP is not about bureaucracy. It is about building trust in our shared ecosystem. I believe if every Implementation Guide follows the same transparent and verifiable process, we create a network of specifications that are reliable, interoperable, and easier to maintain.

At Firely, we believe that open standards only thrive when supported by open tools. Simplifier helps organizations of every size not just publish FHIR resources, but do so in a way that stands up to global scrutiny and earns community trust.

Because in the end, FCP isn’t about getting a sticker. It’s about ensuring that what we build today will still work — reliably, transparently, and collaboratively — tomorrow.

Can we help your organization become FCP compliant?

Get in touch or start exploring Simplifier.net, and let’s make your next Implementation Guide FCP compliant.

You may also want to check out the recording of my presentation I gave at the FHIR North 2025 conference where I discuss what the FHIR Community Process is and how Simplifier enables you to comply with it.

And finally, join our webinar on Jan 20, 2026 if you’d like to learn more!