Oriel — AI & technology worth noticing, every day.

Part 5: The Control That Protected an Empty Bucket

Post · https://dev.to/ndcodes/part-5-the-control-that-protected-an-empty-bucket-e1j

This is Part 5 of a series building an HL7 v2 to FHIR R4 interoperability service in public. The...

First seen by Oriel on .

AI summary

This Part 5 audit compares security documentation with the implementation, exposing controls that were real but disconnected from patient data, and documenting fixes plus unresolved risks.

  • The S3 lifecycle rule protected an unused bucket, while dead-lettered raw HL7 messages used an unwritable Docker volume or ephemeral Kubernetes storage without retention or durability.
  • pds-client exposed NHS numbers through structured logs and request headers; trace propagation replaced patient identifiers, with tests checking serialized output rather than log records.
  • Eight alert runbook links were broken, Terraform classification tags existed only in comments, and POST /hl7 lacked a 256 KiB body limit.
  • Authentication remains unimplemented, and dead-letter retention still depends on application activity despite a 72-hour policy and monitoring.
  • Claude Code helped audit claims but also reproduced faulty asynchronous breaker and metric tests, showing that running the system was necessary to find failures.

#hl7 #fhir #data protection #observability

Generated by gpt-5.6-sol. Check the original for details.

Metric trends

Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained

Reactions

Total public reactions reported by the source; distinct from points and likes.

  • DEV Community: 26, latest observation ; +5 over observed period since

Comments

Comment count reported by the source.

  • DEV Community: 4, latest observation ; 0 over observed period since

Aliases

SourceExternal IDURL
DEV Community5015013https://dev.to/ndcodes/part-5-the-control-that-protected-an-empty-bucket-e1j Read discussion