Validation in .NET and Java: Questions
summary
Shows how a .NET Core app adds the STU3 NuGet and ships specification.zip with the app so the validator finds structure definitions, constructs a Patient, runs validation and returns an enhanced operation outcome with success/fail/warning counts (active=false triggers "element must not be empty", active=true yields success). Explains snapshot generation, option to skip expensive terminology checks, a plan to let users toggle rule sets, and points to the Java command‑line validator jar that calls TX.fhir.org and to the Firestarters GitHub samples for runnable examples.
AI-written summary · about
chapters (6)
- 0:00Introduction and Q&A setup
- 1:04Demo of .NET validation setup
- 10:17Validator settings and modular rules
- 15:19Command-line validator tool demo
- 20:37Questions about Java and Happy validator
- 25:07Future improvements in .NET API
related talks
51m.NET Community Toolkits
42mBuilding a FHIR app with .NET
53mEnforce Coding Standards in .NET: Overcome Broken Window Syndrome
02h 03mBringing the .NET SDK to the cloud
01h 01mASP.NET Basics for Experts
58mSecuring your .NET application software supply-chain
05h 43m.NET Conf 2023 - Student Zone
02h 10mLet's Build: Introduction Firely .NET SDK for FHIR