Bringing the .NET SDK to the cloud
summary
Firely turns the .NET FHIR validator into an AWS Lambda function, shipping compiled .NET DLLs plus a precompiled conformance archive (CAR) that converts IG npm packages into a single SQLite file of element schemas, value‑set tables and precomputed snapshots. The validator keeps firepath and a lightweight terminology service in‑process, accepts FHIR JSON or blob URLs, returns OperationOutcome JSON, and integrates with Black Pear step functions for composable pipelines. The system runs in beta, solves cold starts and invalid metadata by compile‑time checks, and is already deployed in AWS.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:50Parts of the Net Sdk
- 9:05Protobuf and Grpc
- 11:17Logging and Telemetry
- 12:14Conformance Archives
- 14:34Build Delivery
- 15:43Composability
- 33:10Add the Validation Rules
- 35:20Error Messages
- 51:09Define an Interface for the Primitive Types
- 59:59Serialization Benchmark
- 1:11:12Bug in the Json Serializer
- 1:51:09Performance Test
related talks
43mThe open-source Firely .NET SDK 5.0 and beyond
51mCQL on Firely: Digital measures for .NET
42mBuilding a FHIR app with .NET
28mThe Serverless Landscape and Event Driven Futures
38mValidation in .NET and Java
59mHow to Build a Cloud Native Application With .NET and AWS
31mGoing FaaSter: Function as a Service at Netflix
50mAWS Serverless with .NET Core