Healthcare Records Platform
Not ReadyHealthcare Records Platform requires expert operational expertise at 'platform engineering team' level. Current readiness estimate is 20%, critical gaps must be resolved before adoption. Consider starting with a simpler scenario and evolving toward this one.
Readiness Score
20%
Blocking Prerequisites
4
Complexity
Expert
Confidence
StrongPrerequisite Checklist
team
Team at 'platform engineering team' maturity level
This scenario is rated 'platform engineering team' complexity.
Gap signal: Team frequently reaches for external help during incidents or struggles to debug multi-system issues independently.
process
Failure mode awareness and runbooks
The team must understand the 6 documented failure modes for this scenario: replication_lag_cascade, lock_contention, schema_migration_lock, config_drift. Each should have a documented detection procedure and runbook.
Gap signal: The team has no documented runbooks for the scenario's failure modes or cannot name them without reference material.
monitoring
Production-grade observability stack
The scenario requires real-time metrics, structured logging, and distributed tracing on all critical components. Alerting must be configured before going live.
Gap signal: No dashboards exist for the critical path metrics in the scenario.
infrastructure
Minimum team maturity: Platform Engineering Team
This scenario has expert operational complexity. It is recommended for Platform Engineering Team teams or higher.
Gap signal: The requirement 'Minimum team maturity: Platform Engineering Team' is not yet in place.
infrastructure
Runbooks and alerting for high-severity risks
4 high-severity risks identified. Each requires a documented runbook, alerting threshold, and on-call response procedure before running in production.
Gap signal: The requirement 'Runbooks and alerting for high-severity risks' is not yet in place.
infrastructure
Event stream operations expertise
This architecture includes event stream infrastructure (Kafka, Kinesis, or similar). Operations requires consumer group management, partition assignment, dead-letter handling, and lag monitoring.
Gap signal: The requirement 'Event stream operations expertise' is not yet in place.
infrastructure
Mitigation for 2 high-risk topology node(s)
Nodes with high or critical risk exposure: Write-Heavy Transactional, PostgreSQL. Each requires documented mitigation before production deployment.
Gap signal: No mitigation strategy is documented for the high-risk nodes in the topology.
Infrastructure Requirements
Apache Kafka
high burdenDistributed event streaming platform designed for high-throughput, fault-tolerant, ordered, and durable log-based messaging between producers and cons
Managed: Amazon MSK (Managed Streaming for Kafka), Confluent Cloud, Azure Event Hubs (Kafka-compatible), Redpanda Cloud
PostgreSQL
medium burdenACID-compliant relational database with strong consistency, JSONB support, full-text search, and mature replication.
Managed: Amazon RDS for PostgreSQL, Amazon Aurora PostgreSQL, Google Cloud SQL for PostgreSQL, Azure Database for PostgreSQL, Supabase, Neon
Redis
low burdenIn-memory key-value store with optional persistence, supporting strings, hashes, lists, sets, sorted sets, and pub/sub.
Managed: Amazon ElastiCache for Redis, Google Cloud Memorystore, Azure Cache for Redis, Redis Cloud, Upstash
Observability Requirements
Monitor replication lag signals
Seed 'Replication Lag Under Write Burst' identifies 4 metrics relevant to replication_lag_cascade. Execution preview confirms this risk manifests under modelled load.
Seed 'Replication Lag Under Write Burst' identifies 4 metrics relevant to replication_lag_cascade. Execution preview confirms this risk manifests under modelled load.
Monitor generic risk probe signals
Seed 'Lock Contention Risk Probe' identifies 2 metrics relevant to lock_contention.
Seed 'Lock Contention Risk Probe' identifies 2 metrics relevant to lock_contention.
Track Lock Contention exposure
Lock Contention has high exposure and affects 1 component. Affects 1 node. (Write-Heavy Transactional)
Lock Contention has high exposure and affects 1 component. Affects 1 node. (Write-Heavy Transactional)
Track Schema Migration Lock exposure
Schema Migration Lock has high exposure and affects 0 components. Affects 0 nodes
Schema Migration Lock has high exposure and affects 0 components. Affects 0 nodes
Track Deadlock exposure
Deadlock has high exposure and affects 1 component. Affects 1 node. (PostgreSQL)
Deadlock has high exposure and affects 1 component. Affects 1 node. (PostgreSQL)
Audit log table growing at > 500K rows/day; INSERT p99 on audit_log > 20ms; autovacuum unable to keep up with dead tuple
This signal indicates the architecture is approaching 'Tier 1: Audit Log Write Throughput'. Likely bottleneck: Audit log receiving one row per record access creates I/O contention with clinical record writes on the same PostgreSQL primary.
Tier 1: Audit Log Write Throughput
pg_locks showing RowExclusiveLock waits on clinical_records or encounter_notes during shift-change peak hours; write p99
This signal indicates the architecture is approaching 'Tier 2: Concurrent Encounter Write Lock Contention'. Likely bottleneck: Multiple clinical staff members writing addenda to the same encounter simultaneously, or two processes updating encounter status concurrently.
Tier 2: Concurrent Encounter Write Lock Contention
Kafka consumer lag growing on FHIR event topics; downstream clinical systems reporting stale data; outbox table accumula
This signal indicates the architecture is approaching 'Tier 3: FHIR Event Streaming Throughput'. Likely bottleneck: FHIR message transformation and Kafka publish throughput falling behind clinical event write volume.
Tier 3: FHIR Event Streaming Throughput
Readiness Action Plan
Satisfy: Team at 'platform engineering team' maturity level
Effort: 1–4 weeks depending on current state · Unblocks: Adoption of Healthcare Records Platform
Satisfy: Failure mode awareness and runbooks
Effort: 1–4 weeks depending on current state · Unblocks: Adoption of Healthcare Records Platform
Satisfy: Production-grade observability stack
Effort: 1–4 weeks depending on current state · Unblocks: Adoption of Healthcare Records Platform
Satisfy: Mitigation for 2 high-risk topology node(s)
Effort: 1–4 weeks depending on current state · Unblocks: Adoption of Healthcare Records Platform
Instrument all critical path components with metrics and alerting
Effort: 1–2 weeks · Unblocks: Safe production adoption and incident response
Validate adoption in a staging environment before production
Effort: 2–4 weeks for thorough staging validation · Unblocks: Production confidence and rollback preparedness
Mitigate risk: Replication Lag Cascade
Effort: 1–3 weeks · Unblocks: Reduces 'Replication Lag Cascade' from blocking adoption
Mitigate risk: Lock Contention
Effort: 1–3 weeks · Unblocks: Reduces 'Lock Contention' from blocking adoption
Readiness assessment is derived from structured scenario and topology knowledge. It provides an evidence-grounded baseline, not a substitute for an actual team capability review or infrastructure audit. Validate each item against your specific environment.