Resources
The Technical Stack
Deep technical depth across the four disciplines healthcare compliance actually requires. Hands-on implementation, not vendor-deck familiarity.
Regulatory & Compliance
- HTI-1 through HTI-4 auditing
- USCDI v3 / v4 conformance
- CMS-9115-F and CMS-0057-F readiness
- MHMDA engineering and HIPAA validation
- State privacy law applicability (CCPA/CPRA, BIPA, breach notification)
- ISTQB quality standards
Interoperability
Standards
- HL7 FHIR R4
- US Core profiles
- SMART on FHIR authorization
- LOINC, SNOMED, RxNorm normalization
FHIR servers shipped to production (5+ years at Opala)
- Intersystems IRIS for Health
- Smile CDR (HAPI under the hood)
- Fire.ly Server
Hands-on implementation, not vendor-deck familiarity.
Extensive use, not shipped
- HAPI FHIR (evaluation, conformance testing, Smile CDR substrate)
Managed FHIR platforms
- GCP Healthcare API
- Azure Health Data Services
- Epic FHIR R4 and MyChart
- Cerner / Oracle Health FHIR
Conformance testing
- ONC Inferno
- HL7 Touchstone
- Postman conformance suites
Cloud & Agentic AI
Cloud platforms (hands-on across all three)
- Google Cloud Platform (Healthcare API, Firestore, KMS, Cloud Run, BigQuery)
- Microsoft Azure (Health Data Services, FHIR service, AKS)
- Amazon Web Services (HealthLake, Comprehend Medical, Lambda, S3)
No platform lock-in. Cloud choice should not dictate compliance posture.
Agentic AI & tooling
- MCP (Model Context Protocol) server design and integration
- Claude Code agentic CLI
- Cursor AI
- Python, TypeScript, Flutter
- Databricks for clinical data workflows
Privacy & QA Engineering
Privacy engineering
- Clinical data de-identification
- Synthetic data generation
- PHI handling and access controls
- LOINC normalization and FHIR resource mapping
QA & security
- QA automation (50,000+ hours delivered)
- LLM-assisted test design
- SOC 2, HIPAA, HITRUST audit workflows
- Defect Prevention Governance framework
How we build: Python, TypeScript & Flutter on GCP with Claude Code agentic workflows, MCP server integrations, and synthetic FHIR test data, never exposing PHI.
Ready to engage the stack?
Start with an intake call so our delivery team can scope your systems, constraints, and endpoints in writing.