HealthData.Interop.Fhir 1.4.3

dotnet add package HealthData.Interop.Fhir --version 1.4.3
                    
NuGet\Install-Package HealthData.Interop.Fhir -Version 1.4.3
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="HealthData.Interop.Fhir" Version="1.4.3" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="HealthData.Interop.Fhir" Version="1.4.3" />
                    
Directory.Packages.props
<PackageReference Include="HealthData.Interop.Fhir" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add HealthData.Interop.Fhir --version 1.4.3
                    
#r "nuget: HealthData.Interop.Fhir, 1.4.3"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package HealthData.Interop.Fhir@1.4.3
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=HealthData.Interop.Fhir&version=1.4.3
                    
Install as a Cake Addin
#tool nuget:?package=HealthData.Interop.Fhir&version=1.4.3
                    
Install as a Cake Tool

HealthData Interoperability for .NET

A runnable reference implementation for HL7 FHIR R4 interoperability on .NET, built on the Firely .NET SDK โ€” with a set of working examples you can read, run, and adapt.

.NET FHIR Version Tests License

๐ŸŒ Documentation & API Reference: Visit GitHub Pages

๐Ÿ“Œ What this project is (and is not)

What it is: An application-layer toolkit and reference implementation for HL7 FHIR R4 interoperability on .NET. It builds on the Firely .NET SDK โ€” Hl7.Fhir.R4 (FHIR client/model) and Firely.Fhir.Validation.R4 (resource validation) โ€” and adds small, testable services on top: patient CRUD, advanced search, FHIR resource validation, CSVโ†’FHIR ETL, SMART on FHIR auth, AI-assisted data mapping (local LLM), HIPAA-oriented security examples (RBAC, consent, audit, PHI masking), and data drift detection.

What it is not: It does not replace a FHIR server, it is not a full EHR, and it is not a FHIR server "engine" or middleware platform. It does not by itself provide certified HIPAA or ONC compliance. Treat it as a starting point and a collection of patterns, not a turnkey or certified product.

Where this fits architecturally: this toolkit's modules assemble the components a hybrid FHIR architecture needs around a FHIR server (data mapping/ETL in module 04, drift detection in module 08, validation in module 03, auth in module 05, RBAC/consent/audit in module 07) โ€” the FHIR server holds the copy, and the legacy/CSV source stays the system of record. It is not a facade (no dynamic per-request translation) and not FHIR-native (nothing here claims the FHIR server as source of truth). If your project needs a different model, treat these modules as a reference for what to build, not a drop-in fit.

Stability: Current version v1.4.3. The project is early-stage; the public API may still change between minor versions. Use HealthData.Interop.Fhir in non-critical or proof-of-concept work until it reaches a stable 2.x line.

Architecture overview

graph TD
    subgraph Data_Sources [Legacy Data Ingestion]
        DS1[(Large-scale CSV/JSON)]
        DS2[(Legacy SQL DB)]
    end

    subgraph This_Repo [Application Layer โ€” this repository]
        direction TB
        M06[06-AI-Validator: local-LLM normalization]
        M03[03-Resource-Validator: Firely SDK validation]
        M04[04-Data-Mapping-ETL: idempotent upsert]

        M06 --> M03
        M03 --> M04
    end

    subgraph Access_Layer [Access & Security Examples]
        M05[05-SMART-on-FHIR: OAuth2/OIDC auth]
        M02[02-Advanced-Query: chained search]
        M07[07-Safeguards Demo: RBAC/consent/audit]
    end

    Data_Sources --> M06
    M04 --> M05
    M05 --> FHIR_Server[(FHIR R4 Server, e.g. HAPI)]
    FHIR_Server <--> M02
    FHIR_Server --> M07
    FHIR_Server --> M08[08-Drift-Detector: read-only reconciliation]

๐Ÿ“Œ What this project demonstrates

A set of working, runnable examples of interoperability patterns related to US Core and SMART on FHIR, plus everyday FHIR integration patterns on top of the Firely .NET SDK:

Module Demonstrates Entry point Key API
01 Basic FHIR Client Patient create + search against a FHIR R4 server src/1-Basic-Client FhirBasicService
02 Advanced Query Chained search; _include/_revinclude to fetch related resources in one query src/02-Advanced-Query AdvancedQueryService
03 FHIR Resource Validation Firely SDK validation against the FHIR R4 spec; US Core profile-declaration checks src/03-Resource-Validator ResourceValidationService, UsCoreConformanceChecker
04 Data Mapping / ETL CSVโ†’FHIR mapping with idempotent upserts (search-then-Conditional-PUT, transaction bundles) src/04-Data-Mapping-ETL EtlPipelineService, FhirPatientMapper
05 SMART on FHIR OAuth2/OIDC client-credentials flow with token caching; SMART ETL import src/05-SMART-on-FHIR SmartOnFhirAuthService, SmartFhirEtlService
06 AI-Assisted Data Mapping Local-LLM (Ollama) normalization of messy records + deterministic guardrails src/06-AI-Data-Validator AiValidatorService, ClinicalGuardrails
07 HIPAA Technical Safeguards Demo RBAC, consent validation, audit logging, PHI masking โ€” HIPAA Security Ruleโ€“oriented examples src/07-HIPAA-Technical-Safeguards-Demo HipaaComplianceOrchestrator, RbacAuth, ConsentManager, AuditLog
08 Data Drift Detector Read-only reconciliation between a legacy source and the synced FHIR copy src/08-Data-Drift-Detector DriftDetectionService

All shared logic lives in src/HealthDataInteropSharedLibrary (published as the HealthData.Interop.Fhir NuGet package); each numbered folder is a small console app that exercises a different scenario.

๐Ÿ“‚ Examples

01 โ€” Basic FHIR Client

Create a Patient on a FHIR R4 server and search for patients by name.

dotnet run --project src/1-Basic-Client
  • Targets the public demo server http://server.fire.ly by default; change the URL in Program.cs to point at your own server.
  • If the server is unreachable, the app prints a network hint and exits gracefully โ€” no crash.
  • Key API: FhirBasicService.CreatePatientAsync(...), FhirBasicService.SearchPatientsByNameAsync("Doe").

Execution Result:

01 Basic FHIR Client

02 โ€” Advanced Query

Chained-parameter search: find Encounter resources by practitioner name, using _include/_revinclude so related resources come back in a single query instead of extra round-trips.

dotnet run --project src/02-Advanced-Query
  • Key API: AdvancedQueryService.SearchEncountersByPractitionerNameAsync("Smith").
  • Targets https://server.fire.ly by default; edit Program.cs for your own server.

Execution Result:

02 Advanced Query

03 โ€” FHIR Resource Validation

Validate FHIR resources against the R4 specification using Firely.Fhir.Validation.R4. The sample intentionally builds an invalid Patient (e.g. BirthDate = "1990-13-45") so you can see real OperationOutcome-style diagnostics.

dotnet run --project src/03-Resource-Validator
  • The FHIR R4 specification (~6MB) is bundled with the library, so full spec validation works offline; if the spec is unavailable, the service falls back to basic structural validation automatically.
  • Key API: ResourceValidationService.Validate(patient), .GetValidationIssues(patient).
  • US Core: UsCoreConformanceChecker.CheckPatientConformance(patient) checks that a Patient declares a US Core profile URI in Meta.Profile (see US Core support below).

Execution Result:

03 Resource Validator

04 โ€” Data Mapping / ETL (CSV โ†’ FHIR)

Maps Data/legacy_patients.csv into FHIR Patient resources and upserts them, so re-running the job updates existing records instead of creating duplicates:

  1. Extract โ€” read CSV rows into typed LegacyPatientRecord records (CsvHelper).
  2. Transform โ€” FhirPatientMapper (Mapperly source generator) maps them to Patient resources, including gender normalization (male/female/f/m โ†’ FHIR AdministrativeGender, unknown โ†’ Unknown).
  3. Load โ€” search by business identifier first, then update via Conditional PUT (ETag) or create; results are grouped into a BundleType.Transaction bundle for atomicity.
dotnet run --project src/04-Data-Mapping-ETL
  • Targets the public test server https://hapi.fhir.org/baseR4 by default and adds test-name markers to imported names; edit Program.cs for your own server.
  • Key API: EtlPipelineService.RunAsync(csvPath) โ†’ (Created, Updated) counts.

Execution Result:

04 Data Mapping ETL

05 โ€” SMART on FHIR

Two pieces:

  • SmartOnFhirAuthService (shared library) โ€” OAuth2/OIDC client-credentials flow with token caching and refresh, plus CreateAuthenticatedFhirClientAsync(url) which returns a ready-to-use authenticated FhirClient.
  • SmartFhirEtlService โ€” a SMART-style ETL import of data/data.csv with a per-run identifier system to avoid duplicate-identifier collisions on shared test servers.
dotnet run --project src/05-SMART-on-FHIR
  • The entry point reads appsettings.json (MeldRx:FhirServerUrl, default https://hapi.fhir.org/baseR4) and performs the ETL import.
  • To exercise the OAuth flow itself, register a client-credentials app with your OIDC provider and use SmartOnFhirAuthService โ€” see src/tests/SmartOnFhirAuthServiceTests.cs for the expected OidcOptions configuration.
  • Demonstrates scope-based access patterns (e.g. openid profile patient/*.read) as used in SMART on FHIR launches.

Execution Result:

05 SMART on FHIR

06 โ€” AI-Assisted Data Mapping (local LLM)

Turns human-typed "noisy" records (e.g. "Mmale, Jhon Doe, 1990-13-45") into FHIR-ready Patient resources using a local LLM (Ollama, llama3) โ€” designed for local inference without sending data to a cloud LLM. The pipeline is deliberately two-stage:

  1. LLM pass โ€” the model maps the raw line into a small JSON DTO (PatientDto).
  2. Deterministic guardrails โ€” ClinicalGuardrails.Validate(dto) rejects logically invalid output (e.g. a future date of birth, non-parseable dates) before anything becomes a FHIR resource. Invalid rows are reported as rejected, not silently written.
dotnet run --project src/06-AI-Data-Validator
  • Requires Ollama running locally with the llama3 model (ollama pull llama3), reachable at http://localhost:11434.
  • LLM output is non-deterministic: guardrails reduce, but do not guarantee, correctness. Output quality depends on the local model you deploy.
  • The AI provider is injected as a plain Func<string, Task<string>>, so you can swap Ollama for any other local model endpoint (see AiValidatorService's constructor).

Execution Result:

06 AI Data Validator

07 โ€” HIPAA Technical Safeguards Demo

โš ๏ธ This is a technical-safeguards demo, not a compliance product. It shows how HIPAA Security Ruleโ€“style controls can be implemented in code. Actual compliance depends on your deployment, operations, and organizational context โ€” nothing in this repository certifies or guarantees HIPAA compliance.

Walks one simulated PHI access request through the full workflow: RBAC check โ†’ patient consent validation (purpose of use) โ†’ audit log entry, with all console output PHI-masked (SafeConsole / PhiMasker).

dotnet run --project src/07-HIPAA-Technical-Safeguards-Demo

Key APIs: HipaaComplianceOrchestrator.ExecutePhiAccessRequest(...), RbacAuth.CanAccessFullPHI(role), ConsentManager.CheckConsent(patientId, purpose), AuditLog.Record(...), PhiEncryptionService (AES-256-GCM).

Execution Result:

07 Safeguards Demo Result

Patient consent (authorization) flow shown in the demo:

flowchart TD
A["User requests FHIR PHI access"]
B{"Check JWT role & identity scope"}

A --> B
B -->|Clinic Staff| C["Load Patient FHIR Consent Resource"]
B -->|Patient Self| Z["Verify JWT patientId match owner"]

C --> D{"Validate consent status & use purpose"}
D -->|Approved & Valid Purpose| E["Allow full PHI access"]
D -->|Denied/Expired/Mismatch| F["Reject & block PHI access"]

E --> G["Write access audit log"]
F --> H["Write denial audit log"]

Z --> I["Enforce self-only data isolation rule"]
I --> E
Safeguards modeled in this demo (45 CFR ยง164.312-style)
Control HIPAA Security Rule (45 CFR) Where to look Status
Access control ยง164.312(a)(1) RbacAuth โ€” 8-role matrix (SysAdmin, Physician, Nurse, FrontDesk, Biller, Insurance, Patient, Auditor), least-privilege defaults Demonstrated in code
Authentication ยง164.312(a)(2)(iii) SmartOnFhirAuthService โ€” OAuth2/OIDC client-credentials, token caching + refresh Demonstrated in code
Encryption at rest ยง164.312(a)(2)(iv) PhiEncryptionService โ€” AES-256-GCM, 12-byte nonce, 16-byte auth tag Demonstrated in code
Audit controls ยง164.312(b) AuditLog โ€” UTC-timestamped JSON entries (who/when/what/where) Demonstrated in code
Integrity controls ยง164.312(c)(1) ResourceValidationService + Conditional PUT (ETag) in the ETL path Demonstrated in code
Transmission security ยง164.312(e)(1) TLS 1.2+ required; strict certificate validation by default (see Security Notice) Enforced by configuration
Consent management ยง164.508 ConsentManager โ€” purpose-of-use checks Demonstrated in code

๐Ÿฅ US Core profile support (demo scope)

This project demonstrates selected interoperability patterns related to US Core and SMART on FHIR:

  • UsCoreProfiles recognizes these profile URIs: us-core-patient, us-core-observation-lab, us-core-observation-vital-signs, us-core-encounter, us-core-condition, us-core-medication-request, us-core-allergyintolerance.
  • UsCoreConformanceChecker.CheckPatientConformance(patient) verifies that a Patient declares one of the expected US Core profile URIs in Meta.Profile; EnsureUsCoreProfile(patient) can attach the Patient profile during ETL.
  • Scope note: this is profile-declaration checking (does the resource carry the right Meta.Profile URI?), not full US Core IG conformance testing, and it does not imply ONC certification.

08 โ€” Data Drift Detector

Read-only reconciliation for hybrid architectures: compares the current legacy source of truth (CSV) field-by-field (name, gender, birth date, phone) against what is actually stored on the FHIR server. Each record ends up as one of three explicit outcomes:

  • In sync
  • Field-level drift โ€” with old vs. new values shown
  • Missing on server โ€” never synced, or deleted

Detection only: module 08 never writes to the FHIR copy; reconciliation is a separate, deliberate step (re-run module 04 or fix manually).

dotnet run --project src/08-Data-Drift-Detector
  • Run module 04 first so the server has a baseline to compare against.
  • Targets https://hapi.fhir.org/baseR4 by default; edit Program.cs for your own server.
  • Key API: DriftDetectionService.Compare(legacyRecord, fhirPatient), DriftReport.Summarize(results).

๐Ÿ›  How to run

Prerequisites

  • .NET 10 SDK โ€” global.json pins 10.0.302; any 10.0.x SDK works if you adjust rollForward. Sample apps target net10.0; the shared library targets net8.0 (usable from .NET 8/9/10 apps).
  • Internet access for the modules that talk to public FHIR test servers (01, 02, 04, 05, 08).
  • Ollama + llama3 for module 06 (ollama pull llama3).
  • (Optional) An OIDC provider with a client-credentials app, if you want to exercise module 05's SmartOnFhirAuthService against a real identity server.

Run a module

git clone https://github.com/memoryfraction/HealthData-Interoperability-Csharp.git
cd HealthData-Interoperability-Csharp

dotnet run --project src/1-Basic-Client
dotnet run --project src/02-Advanced-Query
dotnet run --project src/03-Resource-Validator
dotnet run --project src/04-Data-Mapping-ETL
dotnet run --project src/05-SMART-on-FHIR
dotnet run --project src/06-AI-Data-Validator
dotnet run --project src/07-HIPAA-Technical-Safeguards-Demo
dotnet run --project src/08-Data-Drift-Detector

Run the tests

dotnet test

180 unit tests (MSTest v3 + FluentAssertions) cover the shared library services โ€” RBAC matrix, consent checks, audit log shape, PHI encryption round-trip, gender normalization, US Core conformance checks, SMART auth option validation, drift comparison, and the FHIR patient mapper.

FHIR spec validation note (module 03): the R4 specification is embedded in the package, so full validation works offline; if it is ever missing, basic structural validation is used as an automatic fallback (no crash).

โš ๏ธ Limitations

  • Early-stage. The public API may still change between minor versions. Use it in non-critical or proof-of-concept work until a stable 2.x line.
  • Not production-certified. Nothing here is a certified HIPAA solution, an ONC-certified product, or a full US Core conformance implementation.
  • No performance benchmarks. There are no reproducible latency/allocation benchmarks in this repository; no performance figures are claimed.
  • Public test servers. Modules 01/02/04/05/08 default to public FHIR test servers (server.fire.ly, hapi.fhir.org) and may create records there. Review the URLs in each Program.cs before running, and never point them at production data without care.
  • Local AI module (06). Output quality depends on the local model; guardrails reject obviously invalid results but cannot guarantee clinical correctness.
  • Scope. These are reference examples for specific scenarios (Patient-centric). They are not a general-purpose FHIR framework.

๐Ÿ“ฆ Dependencies

Package Version Used for
Hl7.Fhir.R4 6.0.2 FHIR R4 client & resource model (Firely .NET SDK)
Firely.Fhir.Validation.R4 3.1.0 FHIR R4 resource validation
CsvHelper 33.1.0 CSV reading in ETL / drift modules
Riok.Mapperly 4.1.1 Compile-time mapping (CSV โ†’ FHIR)
IdentityModel 7.0.0 OAuth2/OIDC client-credentials (SMART on FHIR)
Polly 8.4.2 Resilience primitives
Serilog 4.3.0 (+ console/file sinks) Structured logging
Microsoft.Extensions.Configuration.Json 10.0.2 appsettings.json config in module 05
Ollama + llama3 โ€” Local LLM for module 06 (optional)

Test stack: MSTest 3.8.3, FluentAssertions 8.5.0.

๐Ÿ” Security notes

  • TLS certificate validation is STRICT by default. A certificate-validation bypass exists only for local development (e.g. self-signed MITM proxy) and is off by default โ€” it activates only if you explicitly set HEALTHDATA_INSECURE_SKIP_TLS=1 before starting the process. Never set it in production; disabling TLS validation conflicts with HIPAA ยง164.312(e)(1) transmission-security requirements.
  • PHI-masked logging. Console/log output passes through PhiMasker: SSN, patient names, dates of birth, phone numbers, and emails are replaced with placeholders before they reach the console or log sinks (SafeConsole, SafeInformation/SafeWarning/SafeError extensions).
  • Local AI (module 06) is designed for local inference without sending data to a cloud LLM. "Local" reduces exposure but is not a guarantee โ€” validate your own threat model before handling real PHI.

๐Ÿ“ฆ NuGet packages

The toolkit is published as 4 packages on nuget.org:

Package Description When to use
HealthData.Interop.Fhir Meta-package โ€” full FHIR R4 toolkit (client, validation, ETL, SMART auth, HIPAA security, drift detection) Most users โ€” install this one
HealthData.Interop.Abstractions Core abstractions โ€” IApplicationLogger, PhiMasker, SafeConsole, Guard. Zero dependencies. You only need PHI masking or logging abstractions
HealthData.Interop.Logging.Extensions Bridge: IApplicationLogger โ†” Microsoft.Extensions.Logging.ILogger (NLog, Serilog, any provider) You use NLog or another ILogger provider and want PHI-masked logging
HealthData.Interop.Logging.Serilog Serilog-backed ConsoleLogger with PHI masking You use Serilog and want the original ConsoleLogger

Quick install (meta-package, includes everything):

Package ID: HealthData.Interop.Fhir ยท License: MIT ยท Target: .NET 8.0 (works on .NET 9/10+)

# Meta-package (recommended โ€” includes everything):
dotnet add package HealthData.Interop.Fhir

# Or install individual packages:
dotnet add package HealthData.Interop.Abstractions          # PHI masking only, zero deps
dotnet add package HealthData.Interop.Logging.Extensions    # NLog / ILogger bridge
dotnet add package HealthData.Interop.Logging.Serilog       # Serilog adapter

Quick start (verified against the current public API):

using HealthDataInteropSharedLibrary.BasicClient;
using HealthDataInteropSharedLibrary.ResourceValidator;

// 1. Point at a FHIR R4 server and search for patients by name.
var service = new FhirBasicService("https://your-fhir-server.com/fhir");
var patients = await service.SearchPatientsByNameAsync("Doe");

foreach (var p in patients)
    Console.WriteLine(FhirBasicService.FormatPatientName(p));

// 2. Validate a Patient resource against the bundled FHIR R4 specification.
var validator = new ResourceValidationService();
if (patients.Count > 0)
{
    var ok = validator.Validate(patients[0]);
    Console.WriteLine(ok ? "Patient is valid against FHIR R4." : "Validation found issues.");
}

๐Ÿ—‚ Repository structure

HealthData-Interoperability-Csharp/
โ”œโ”€โ”€ src/
โ”‚   โ”œโ”€โ”€ 1-Basic-Client/                     # 01: patient create + search
โ”‚   โ”œโ”€โ”€ 02-Advanced-Query/                  # 02: chained search / _include
โ”‚   โ”œโ”€โ”€ 03-Resource-Validator/              # 03: FHIR R4 spec validation
โ”‚   โ”œโ”€โ”€ 04-Data-Mapping-ETL/                # 04: CSV โ†’ FHIR upsert
โ”‚   โ”œโ”€โ”€ 05-SMART-on-FHIR/                   # 05: OAuth2/OIDC + ETL
โ”‚   โ”œโ”€โ”€ 06-AI-Data-Validator/               # 06: local-LLM normalization
โ”‚   โ”œโ”€โ”€ 07-HIPAA-Technical-Safeguards-Demo/ # 07: RBAC/consent/audit demo
โ”‚   โ”œโ”€โ”€ 08-Data-Drift-Detector/             # 08: read-only reconciliation
โ”‚   โ”œโ”€โ”€ Abstractions/                       # HealthData.Interop.Abstractions (NuGet)
โ”œโ”€โ”€ Logging.Extensions/                 # HealthData.Interop.Logging.Extensions (NuGet)
โ”œโ”€โ”€ Logging.Serilog/                    # HealthData.Interop.Logging.Serilog (NuGet)
โ”œโ”€โ”€ HealthData.Interop.Fhir/            # HealthData.Interop.Fhir meta-package (NuGet)
โ”‚   โ””โ”€โ”€ tests/                              # MSTest v3 unit tests (180 tests)
โ”œโ”€โ”€ docs/                                   # CodeStandard, RBAC design doc, CN readme
โ”œโ”€โ”€ pages/                                  # GitHub Pages documentation site
โ””โ”€โ”€ images/                                 # execution screenshots

๐Ÿ“ Changelog

See CHANGELOG.md for version history.

Project Description
Clinic FHIR Server A multi-tenant FHIR R4 server for clinics and community health centers: tenant-isolated FHIR storage, role-based access control, audit logging, and PHI encryption.
XBridge A Prior Authorization toolkit that validates X12 278 transactions against payer Companion Guide rules and converts between X12 and FHIR R4, running entirely in your browser locally.
Quant.Infra.Net One-stop .NET quantitative trading infrastructure โ€” multi-source data ingestion, unified broker execution, portfolio analytics.
LLSDA Open-source lightning location system (LLS) data analysis library โ€” published on NuGet, cited in a TechRxiv preprint.

More projects by the same author: github.com/memoryfraction

โ˜• Collaboration

Working on FHIR / healthcare interoperability and think we could help each other? Reach out by email or book a meeting.

๐ŸŽ Free: The FHIR R4/R5 Compliance Checklist

The 12 pitfalls teams hit on the road to 21st Century Cures Act certification โ€” in one printable PDF. Get the checklist, plus occasional deep-dives on healthcare interoperability. No spam, unsubscribe anytime.

๐Ÿ“ง Subscribe โ€” Get the Free US Healthcare Checklist

๐Ÿ‘ค Contact

Rong (Rex) Fan โ€” .NET/C# ยท healthcare interoperability (FHIR/HL7) ยท AI engineering

๐Ÿ“„ License

MIT โ€” this repository is intended as a reference implementation and educational resource. You are free to read, copy, and adapt the code; see the LICENSE file for the full terms. No warranty of any kind.

๐Ÿ™Œ Support this work

If this work is helpful to you, feel free to send a small gift โ€” it helps support my work and keep the project maintained.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.4.3 148 9/22/2026
1.4.2 107 9/22/2026
1.3.5 132 9/7/2026
1.3.4 131 9/3/2026
1.3.3 270 8/11/2026
1.3.2 119 8/11/2026
1.3.1 131 8/11/2026
1.3.0 140 8/11/2026

v1.4.3 - Package metadata: added Title, HIPAA-aware description wording with an as-is disclaimer, and healthcare/interoperability tags. No code changes.