Most health systems treat clinical data standards as an IT decision. openEHR reframes it as a clinical governance imperative.
Insights
Thought Leadership & Technical Perspectives
Practitioner perspectives on healthcare technology, clinical data standards, and platform implementation.
The platform is not the problem. The pattern of failures traces back to three recurring decisions made before day one.
Technical deployment is the easy part. Governance, liability, and clinical workflow integration determine whether AI actually helps.
Moving CDS Hooks from sandbox to production requires navigating latency constraints, EHR vendor politics, and clinical adoption challenges.
A practitioner walkthrough of implementing the Da Vinci PAS guide, including the decisions that matter most for payer organizations.
The standards community treats these as opposing camps. In practice, the strongest clinical data architectures use both deliberately.
Agentic AI moves beyond text generation to execute multi-step clinical tasks autonomously. Understanding the distinction is essential before deployment.
The CMS Interoperability and Prior Authorization Final Rule establishes binding API and timeline requirements that payers can no longer defer.
TEFCA provides the legal and technical foundation for nationwide health data exchange. In 2026, participation decisions have real strategic consequences.
Agentforce brings autonomous AI workflow execution to the Salesforce platform. For healthcare organizations, the value depends entirely on implementation architecture.
The proposed HIPAA Security Rule update eliminates addressable encryption requirements and mandates specific technical controls for the first time in two decades.
ServiceNow's healthcare modules bridge clinical operations and IT service management. Integration with Epic and other EHR platforms determines how much value the platform can deliver.
Both platforms serve healthcare organizations well, but for fundamentally different purposes. The most common mistake is choosing before defining the problem.
A population health analytics platform is not a data warehouse with clinical data in it. The architectural differences determine whether analytics actually drive care delivery.
RPM has matured from a post-discharge intervention to a continuous care infrastructure. The clinical and data architecture required to support this shift is substantial.
AI-driven search is changing how healthcare organizations and buyers find information. Optimizing for answer engines requires different content architecture than traditional SEO.
Ready to Start?
Most healthcare IT projects fail because of who's not in the room.
At Selah, you talk to the person who will actually do the work โ from the first call to go-live. No account managers. No bait-and-switch. No surprises.