FHIR meets corporate security
summary
CDS Hooks integration breaks when enterprise gateways strip or front TLS and prevent verifying client JWTs, forcing workarounds like use access token to fetch cert or fallback to managed client-id/password. Patient identifiers often must be obfuscated, requiring either persisted remapped IDs in a FHIR repository or a durable mapping service for a FHIR facade so that 789 maps reliably to 1234 or data breaks. Forensic tracing needs an injected tracker (hashed or encrypted), with key management and retrieval costs that may outweigh benefit.
AI-written summary · about
chapters (6)
- 0:00Introduction and setup
- 1:06About the speaker
- 3:59CDS Hooks dilemma
- 8:10Sensitivity of patient ID
- 12:25Forensic data tracking
- 16:41Q&A session
related talks
43mSecurity in FHIR
01h 04mApisecure, 14 & 15 March 2023 - Grahame Grieve, Principal at Health Intersections Pty Ltd.
45mApisecure, 14 & 15 March 2023 - John Moehrke, Co-Chair at Security Working Group.
42mRemote Decision Support with CDS Hooks
01h 01mSharing Health Information Through APIs
42mReferential Integrity
42mFHIR for clinicians
34mFHIR Projects