babelfhir-ts 1.0.41 → 1.0.43

package/README.md

@@ -4,7 +4,8 @@
 
 # BabelFHIR-TS
 
-[![npm version](https://img.shields.io/npm/v/babelfhir-ts.svg)](https://www.npmjs.com/package/babelfhir-ts)
+[![npm: babelfhir-ts](https://img.shields.io/npm/v/babelfhir-ts.svg?label=babelfhir-ts)](https://www.npmjs.com/package/babelfhir-ts)
+[![@babelfhir-ts/client-r4](https://img.shields.io/npm/v/@babelfhir-ts/client-r4.svg?label=%40babelfhir-ts%2Fclient-r4)](https://www.npmjs.com/package/@babelfhir-ts/client-r4)
 [![License: ISC](https://img.shields.io/badge/License-ISC-blue.svg)](https://opensource.org/licenses/ISC)
 [![TypeScript](https://img.shields.io/badge/TypeScript-5.8-blue)](https://www.typescriptlang.org/)
 [![Node.js](https://img.shields.io/badge/Node.js-18%2B-green)](https://nodejs.org/)
@@ -20,6 +21,7 @@
 - **Random data builders** for testing and development (when class generation is enabled)
 - **Zero manual mapping**—consume any FHIR package or Implementation Guide directly from registries
 - **Fast and lightweight**—minimal runtime deps; only `fhirpath` is required for validators
+- **Type-safe FHIR client** — generated client extends [`@babelfhir-ts/client-r4`](https://www.npmjs.com/package/@babelfhir-ts/client-r4) with profile-specific methods (e.g., `.usCorePatient()`, `.pASClaim()`) on top of 145 base R4 resource accessors
 - **Install any FHIR profile as a node module**—use `babelfhir-ts install` to add Implementation Guides directly to your project
 
 <!-- PARITY-BADGES:START - Do not remove or modify this section -->
@@ -46,25 +48,27 @@ Every pull request runs two independent CI pipelines that validate generated cod
 
 ### Validation with Firely .NET SDK
 
-The first pipeline validates generated resources using the [Firely .NET SDK validator](https://docs.fire.ly/projects/Firely-NET-SDK/) (v3.0.1). Results are published as live badges:
+The first pipeline validates generated resources using the [Firely .NET SDK validator](https://docs.fire.ly/projects/Firely-NET-SDK/) (v3.1.0). Results are published as live badges:
 
 ![US Core 8.0.0](https://img.shields.io/endpoint?url=https://max-health-inc.github.io/BabelFHIR-TS/badges/badge-us-core.json)
 ![ISiK Basis 4.0.3](https://img.shields.io/endpoint?url=https://max-health-inc.github.io/BabelFHIR-TS/badges/badge-isik-basis.json)
 ![IPS 2.0.0](https://img.shields.io/endpoint?url=https://max-health-inc.github.io/BabelFHIR-TS/badges/badge-ips.json)
 ![SMART 2.2.0](https://img.shields.io/endpoint?url=https://max-health-inc.github.io/BabelFHIR-TS/badges/badge-smart.json)
 ![CH Core 5.0.0](https://img.shields.io/endpoint?url=https://max-health-inc.github.io/BabelFHIR-TS/badges/badge-ch-core.json)
+![DaVinci PAS 2.0.1](https://img.shields.io/endpoint?url=https://max-health-inc.github.io/BabelFHIR-TS/badges/badge-davinci-pas.json)
 
 > 11 profiles are excluded from this pipeline due to schema loading issues in the Firely SDK. These profiles validate successfully with the HL7 Java Validator below. Details in [docs/FIRELY-VALIDATOR-BUGS.md](./docs/FIRELY-VALIDATOR-BUGS.md).
 
 ### Validation with HL7 Java Validator
 
-The second pipeline validates using the [official HL7 FHIR Validator](https://confluence.hl7.org/display/FHIR/Using+the+FHIR+Validator) (v6.3.11), the reference implementation for FHIR conformance checking:
+The second pipeline validates using the [official HL7 FHIR Validator](https://confluence.hl7.org/display/FHIR/Using+the+FHIR+Validator) (v6.9.1), the reference implementation for FHIR conformance checking:
 
 ![US Core 8.0.0](https://img.shields.io/endpoint?url=https://max-health-inc.github.io/BabelFHIR-TS/badges/badge-hl7-us-core.json)
 ![ISiK Basis 4.0.3](https://img.shields.io/endpoint?url=https://max-health-inc.github.io/BabelFHIR-TS/badges/badge-hl7-isik-basis.json)
 ![IPS 2.0.0](https://img.shields.io/endpoint?url=https://max-health-inc.github.io/BabelFHIR-TS/badges/badge-hl7-ips.json)
 ![SMART 2.2.0](https://img.shields.io/endpoint?url=https://max-health-inc.github.io/BabelFHIR-TS/badges/badge-hl7-smart.json)
 ![CH Core 5.0.0](https://img.shields.io/endpoint?url=https://max-health-inc.github.io/BabelFHIR-TS/badges/badge-hl7-ch-core.json)
+![DaVinci PAS 2.0.1](https://img.shields.io/endpoint?url=https://max-health-inc.github.io/BabelFHIR-TS/badges/badge-hl7-davinci-pas.json)
 
 > Terminology validation requires a tx server. The pipeline uses `--tx-server https://tx.fhir.org/r4` during generation to expand ValueSets and produce valid codes.
 
@@ -74,48 +78,27 @@ The second pipeline validates using the [official HL7 FHIR Validator](https://co
 
 ## Installation
 
-Install globally (recommended when using the CLI frequently):
-
 ```bash
 npm install -g babelfhir-ts
 ```
 
-Or invoke on-demand without a global install:
-
-```bash
-npx babelfhir-ts --help
-```
-
-> **Requirements:** Node.js 18+ (ESM support) and an internet connection when downloading packages from remote registries.
+Or on-demand: `npx babelfhir-ts --help`
 
-## Quick start
+> **Requirements:** Node.js 18+ and an internet connection for remote registries.
 
-Generate code from a local folder that contains FHIR packages:
+## Quick Start
 
 ```bash
+# Generate from a local folder
 babelfhir-ts input/ output/
-```
-
-Process a single package archive and write the generated interfaces back into a new `.tgz` file:
-
-```bash
-babelfhir-ts hl7.fhir.us.core-8.0.0.tgz us-core-generated.tgz
-```
 
-Download and process a package directly from a registry (defaults to `https://packages.simplifier.net`):
-
-```bash
+# Download and process from a registry
 babelfhir-ts --package hl7.fhir.us.core@8.0.0
-```
-
-Download, process and install a processed package into your current project:
 
-```bash
+# Install as a project dependency
 babelfhir-ts install hl7.fhir.us.core@8.0.0
 ```
 
-After generation you can import the emitted classes:
-
 ```ts
 import { USCorePatientClass } from "./output/USCorePatientClass";
 
@@ -123,159 +106,82 @@ const patient = USCorePatientClass.random();
 const { errors, warnings } = await patient.validate();
 ```
 
-## Using the generated code in your project
-
-Generated profile packages installed via `babelfhir-ts install` are published as **compiled JavaScript with TypeScript declarations**:
-
-- JavaScript for runtime: `index.js`, `*.js`
-- Type declarations for IDE/TS: `index.d.ts`, `*.d.ts`
-- Dependencies:
-  - `@types/fhir` is included as a dependency of the generated package (no extra setup in your app)
-  - `fhirpath` is a peer dependency (required only if you use the generated validators/classes)
-
-Install `fhirpath` in your app if you plan to call `.validate()` or use the generated classes.
-
-### Module resolution
-
-Generated packages work with all modern TypeScript setups:
-
-- **Node.js 18+** with `"type": "module"` in `package.json`
-- **Bundlers** (Vite, esbuild, Webpack) with ESM output
-- **TypeScript 5.0+** with any module resolution (`node16`, `nodenext`, or `bundler`)
-
-#### FHIR type imports
-
-Generated code imports base FHIR types from `"fhir/r4"`:
-
-```ts
-import { Appointment, Extension, CodeableConcept } from "fhir/r4";
-```
-
-Since `@types/fhir` doesn't provide a `package.json` `exports` field, BabelFHIR-TS includes an **ambient module declaration** (`fhir-r4.d.ts`) in every generated package. The generated `index.d.ts` references this file:
-
-```ts
-/// <reference path="./fhir-r4.d.ts" />
-```
-
-This ensures TypeScript can resolve `fhir/r4` imports automatically without any configuration in your project's `tsconfig.json`.
-
-## CLI reference
+## CLI Reference
 
+<!-- CLI_HELP_START -->
 ```
-babelfhir-ts [options] [<input> [output]]
+BabelFHIR-TS: Generate TypeScript interfaces from FHIR StructureDefinitions
+
+Usage:
+  babelfhir-ts [options] [<input> [output]]
+  babelfhir-ts install [--package] <pkg@version|path> [--registry <url>] [options]
+
+Arguments:
+  input   Input can be:
+          - Canonical URL of a FHIR profile (http://... or https://...)
+          - Directory containing FHIR packages (.tgz/.zip files)
+          - Single FHIR package (.tgz/.zip file)
+          - Single StructureDefinition (.json file)
+          - Directory containing StructureDefinition files
+  output  Output directory or archive name (optional)
+
+Commands:
+  install                Download, process, and npm install package as dependency
+
+Options:
+  -h, --help               Show this help message
+  -v, --version            Show version number
+  --log <dest>             Log destination: console (default) or file
+  --log-level <level>      Log verbosity: error, warn, info (default), or debug
+  --cache-dir <path>       Custom cache directory (default: .cache, env: FHIR_CACHE_ROOT)
+  --no-cache               Delete .cache folder after generation
+  --no-classes             Only generate interfaces and types (skip class generation)
+  --no-client              Skip FHIR client generation (client generated by default)
+  --package <pkg@version>  Download FHIR package from registry and process it
+  --registry <url>         FHIR package registry URL (default: https://packages.simplifier.net)
+  --tx-server <url>        Terminology server URL for ValueSet expansion (e.g., https://tx.fhir.org/r4)
+                           When set, expands ValueSets without explicit codes using $expand operation
+
+Examples:
+  babelfhir-ts                                             # Process ./input to ./output
+  babelfhir-ts http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient  # Generate from profile URL
+  babelfhir-ts package.tgz                                 # Process package to current directory
+  babelfhir-ts package.tgz modified-package.tgz            # Embed interfaces in package
+  babelfhir-ts profiles/ generated/                        # Process directory to directory
+  babelfhir-ts --package hl7.fhir.us.core@8.0.0            # Download and process from default registry
+  babelfhir-ts --package hl7.fhir.us.core@8.0.0 output/    # Download and output to directory
+  babelfhir-ts --package pkg@version --log console --log-level debug  # With verbose logging
+  babelfhir-ts install de.gematik.isik-basismodul@3.1.0                   # Download, process, and npm install
+  babelfhir-ts install ./package.tgz                                      # Install from local package file
+  babelfhir-ts install hl7.fhir.us.core@8.0.0 --registry <url>            # Install from custom registry
+  babelfhir-ts install --package hl7.fhir.us.core@8.0.0 --registry <url>  # Alternative syntax
 ```
+<!-- CLI_HELP_END -->
 
-| Argument / option           | Description                                                                                                                                                         |
-| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `<input>`                 | Directory of FHIR packages/StructureDefinitions, single package (`.tgz`/`.zip`), or single StructureDefinition `.json`. Defaults to `./input` when omitted. |
-| `<output>`                | Destination directory or archive. Defaults to `./output` when omitted.                                                                                            |
-| `install`                 | Downloads, processes, and installs a package as a project dependency.                                                                                               |
-| `--package <pkg@version>` | Fetch a package from a registry and process it without manual download.                                                                                             |
-| `--registry <url>`        | Custom registry base URL (default:`https://packages.simplifier.net`).                                                                                             |
-| `--tx-server <url>`       | Terminology server URL for ValueSet expansion (e.g., `https://tx.fhir.org/r4`). When set, expands ValueSets without explicit codes using the `$expand` operation. |
-| `--log <level>`           | Control logging output:`none` (default), `console`, or `file`.                                                                                                |
-| `--no-cache`              | Remove the `.cache` directory once generation completes.                                                                                                          |
-| `--no-classes`            | Skip emitting helper classes (interfaces & validators only).                                                                                                        |
-| `--cache-dir <path>`      | Custom cache directory (default:`.cache`). Also configurable via `FHIR_CACHE_ROOT` env var.                                                                     |
-| `-h, --help`              | Print usage help.                                                                                                                                                   |
-| `-v, --version`           | Print the BabelFHIR-TS version.                                                                                                                                     |
-
-### Supported inputs
-
-- **Directory** – scan all `.tgz`, `.zip`, or `.json` files inside the folder
-- **Archive** – process a FHIR NPM package in `.tgz` or `.zip` format
-- **StructureDefinition JSON** – generate code for a single profile definition
-
-## Scripts for contributors
-
-| Script                      | Purpose                                                                      |
-| --------------------------- | ---------------------------------------------------------------------------- |
-| `npm run generate`        | Execute the CLI against the local `input/` folder and refresh `output/`. |
-| `npm run generate:check`  | End-to-end check: generate, type-check, and lint the emitted output.         |
-| `npm test`                | Type-check and run all Vitest suites (coverage enabled).                     |
-| `npm test pipelineParity` | Run pipeline parity tests against Firely .NET SDK validator.                 |
-
-## Caching notes
-
-The generator caches downloaded StructureDefinitions and packages inside `.cache/`. When you need a clean run, pass `--no-cache` or manually remove the folder. Temporary downloads land in `.temp-*` directories and are cleaned up automatically.
-
-## Why BabelFHIR-TS?
-
-**The FHIR Challenge**: Implementation Guides define strict profiles that constrain base FHIR resources with required or must-support elements, custom extensions, value set bindings, and cardinality rules. Existing TypeScript libraries can't capture these requirements when you need profile-specific types, leading to an overhead when using TypeScript to build apps that interact with FHIR servers.
-
-**The BabelFHIR-TS Solution**: Automatically generates TypeScript interfaces and validation logic directly from StructureDefinition JSON. Your IDE autocompletes required fields, flags missing extensions at compile-time, and validates FHIRPath invariants at runtime.
-
-## Limitations
-
-BabelFHIR-TS is a code generation tool that parses FHIR StructureDefinitions and produces TypeScript interfaces and validators. While it handles many common FHIR profiling patterns, there are important limitations to be aware of:
-
-### Profile Mapping Accuracy
-
-- **Not guaranteed for all IGs**: The generator uses heuristics to interpret StructureDefinition constraints, slicing rules, and extensions. Complex or unusual profiling patterns may not map correctly to TypeScript.
-- **Test before production**: Always validate the generated code against your specific Implementation Guide's examples and test cases. We recommend running the official FHIR validator alongside BabelFHIR-TS in your QA pipeline.
-- **Edge cases**: Rare profiling constructs (deeply nested slicing, conditional constraints, complex discriminators) may generate suboptimal or incomplete types.
-
-### Validation Scope
-
-The generated `validate()` methods DO check:
+## Documentation
 
-- **FHIRPath constraints** from StructureDefinition invariants
-- **Cardinality rules** (min/max occurrences)
-- **Required fields** from profiles
-- **Pattern constraints** (patternCodeableConcept, patternCoding)
-- **Slice validation** for common patterns (coding arrays, BackboneElement slices)
-- **Data type correctness** (string, number, boolean, etc.)
+Full documentation is available at **[max-health-inc.github.io/BabelFHIR-TS/docs/](https://max-health-inc.github.io/BabelFHIR-TS/docs/)**
 
-The generated validators DO NOT check:
-
-- **Terminology validation** (ValueSet expansion, code system membership) - requires terminology server
-- **Reference resolution** (checking that referenced resources exist) - requires FHIR server
-- **Complex discriminator types** (type, profile, exists, position) - only pattern/value discriminators supported
-- **Cross-resource business rules** - application-specific logic
-
-For comprehensive conformance testing, use the official [HL7 FHIR Validator](https://confluence.hl7.org/display/FHIR/Using+the+FHIR+Validator)!
-
-### TypeScript Limitations
-
-- **Runtime type checking is limited**: TypeScript types are erased at compile time. The generated interfaces provide compile-time safety but cannot enforce constraints at runtime without the validator functions.
-- **Extension slicing**: While the generator creates typed extension interfaces, TypeScript cannot enforce that extension arrays contain exactly the required slices at compile time (this is validated at runtime).
-- **Choice types**: FHIR's `[x]` choice types (e.g., `value[x]`) are represented as union types in TypeScript, which may require runtime type narrowing.
-
-### Generated Helper Methods
-
-- **`random()` is not fully conformant**: The generated `.random()` methods create test data that satisfies TypeScript types and basic cardinality, but **do not guarantee** fully valid FHIR resources. Random data may violate:
-
-  - Complex FHIRPath invariants
-  - ValueSet bindings (codes are randomly chosen from required bindings but not guaranteed to be semantically correct)
-  - Profile-specific business rules
-  - Reference integrity constraints
-
-  Use `random()` for development, testing, and prototyping, but always validate production data on the FHIR server side.
-- **`validate()` coverage**: The generated validation methods execute FHIRPath expressions and check constraints from StructureDefinitions. They are tested against the HL7 Java Validator and the Firely .NET SDK for the Implementation Guides listed in the [Continuous Validation](#continuous-validation) section. Edge cases, complex slicing patterns, or profiles not in the CI pipeline may produce different results. For production conformance testing, use the official [HL7 FHIR Validator](https://confluence.hl7.org/display/FHIR/Using+the+FHIR+Validator) as the source of truth.
-
-### FHIR Version Support
-
-- **R4 only**: The current version targets FHIR R4. Support for R5, DSTU2, or STU3 is not yet available.
-- **Dependencies**: Generated code depends on `@types/fhir` (R4 definitions) and `fhirpath` (R4 compatible).
-
-### Reporting Issues
-
-If you encounter an Implementation Guide that doesn't generate correctly, please [open an issue](https://github.com/Max-Health-Inc/BabelFHIR-TS/issues) with:
-
-- The package name and version
-- The specific StructureDefinition URL
-- Expected vs. actual generated output
-- Any validation errors or type mismatches
-
-We continuously improve the generator based on real-world IG usage, and your feedback helps make BabelFHIR-TS more robust.
+- [Getting Started](https://max-health-inc.github.io/BabelFHIR-TS/docs/getting-started) — installation, quick start, first generation
+- [CLI Reference](https://max-health-inc.github.io/BabelFHIR-TS/docs/cli-reference) — full list of commands and options
+- [Generated Code Guide](https://max-health-inc.github.io/BabelFHIR-TS/docs/generated-code) — understanding the output, module resolution, FHIR type imports
+- [FHIR Client](https://max-health-inc.github.io/BabelFHIR-TS/docs/fhir-client) — type-safe server interactions
+- [Validation](https://max-health-inc.github.io/BabelFHIR-TS/docs/validation) — what validators check, CI pipelines, known Firely SDK issues
+- [Limitations](https://max-health-inc.github.io/BabelFHIR-TS/docs/limitations) — R4 only, edge cases, random() caveats
+- [Contributing](https://max-health-inc.github.io/BabelFHIR-TS/docs/contributing) — dev setup, scripts, project structure
 
 ## License
 
 ISC © Maximilian Nussbaumer
 
+## Changelog
+
+Release notes are published automatically on GitHub Releases:
+**[View all releases](https://github.com/Max-Health-Inc/BabelFHIR-TS/releases)**
+
 ## Contributing
 
-Contributions are welcome! Please read [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines on how to contribute to this project.
+Contributions are welcome! See the [Contributing guide](https://max-health-inc.github.io/BabelFHIR-TS/docs/contributing) for dev setup, scripts, and how to submit changes.
 
 ## Security
 
@@ -283,7 +189,9 @@ For security issues, please see [SECURITY.md](SECURITY.md) for our security poli
 
 ## Links
 
-- [npm package](https://www.npmjs.com/package/babelfhir-ts)
+- [npm package — babelfhir-ts](https://www.npmjs.com/package/babelfhir-ts)
+- [npm package — @babelfhir-ts/client-r4](https://www.npmjs.com/package/@babelfhir-ts/client-r4)
 - [GitHub repository](https://github.com/Max-Health-Inc/BabelFHIR-TS)
+- [Validation report](https://max-health-inc.github.io/BabelFHIR-TS/)
 - [Issue tracker](https://github.com/Max-Health-Inc/BabelFHIR-TS/issues)
 - [Changelog](CHANGELOG.md)

package/out/src/generator/base-r4/README.md

@@ -0,0 +1,28 @@
+# Bundled Base R4 StructureDefinitions
+
+This directory contains offline copies of FHIR R4 StructureDefinitions that the generator needs but cannot reliably fetch at runtime.
+
+## Why?
+
+The generator resolves StructureDefinition dependencies via network (hl7.org, Simplifier, etc.). However, some SDs are hosted on servers that are frequently unreliable — especially in CI environments. When `sdParser.ts` cannot find a SD via local cache or network fetch, it falls back to these bundled files as a last resort.
+
+## How discovery works
+
+Rather than a hardcoded URL-to-file map, `sdParser.ts` auto-discovers all `.json` files in this directory at runtime. For each file it reads the `url` field from the JSON and builds a lookup map. For standard FHIR base SDs (`http://hl7.org/fhir/StructureDefinition/...`), the `/R4/` URL variant is also registered automatically.
+
+## Adding a new bundled SD
+
+1. Place the StructureDefinition JSON file in this directory.
+2. Ensure it has a valid `url` field (the canonical URL).
+3. That's it — `discoverBundledBaseSds()` in `sdParser.ts` picks it up automatically.
+
+## Current contents
+
+| File | Canonical URL | Reason |
+|------|---------------|--------|
+| `Bundle.json` | `http://hl7.org/fhir/StructureDefinition/Bundle` | Core R4 base type — required by many IGs for document/transaction bundles |
+| `Composition.json` | `http://hl7.org/fhir/StructureDefinition/Composition` | Core R4 base type — required by document-based IGs (CH Core, ISiK, etc.) |
+| `Endpoint.json` | `http://hl7.org/fhir/StructureDefinition/Endpoint` | Core R4 base type — required by ISiK profiles |
+| `Subscription.json` | `http://hl7.org/fhir/StructureDefinition/Subscription` | Core R4 base type — required by ISiK profiles |
+| `ValueSet.json` | `http://hl7.org/fhir/StructureDefinition/ValueSet` | Core R4 base type — used when generating ValueSet profiles |
+| `backport-subscription.json` | `http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-subscription` | Cross-version IG (R4B) — ISiK profiles extend this; not available on standard R4 servers |

package/out/src/generator/base-r4/well-known-system-codes.json

@@ -0,0 +1,63 @@
+{
+  "_description": "Curated sample codes for large external CodeSystems (LOINC, SNOMED CT, etc.) that cannot be shipped in full due to size or licensing. Used as fallback when the CodeSystem has content='not-present' to allow ValueSet resolution for core R4 ValueSets like observation-codes without requiring a terminology server.",
+  "_valueSets": "Maps core R4 ValueSet canonical URLs to included CodeSystem URLs. Used when the dependency package containing the ValueSet is not cached locally.",
+  "systems": {
+    "http://loinc.org": [
+      { "code": "29463-7", "display": "Body weight" },
+      { "code": "8302-2", "display": "Body height" },
+      { "code": "85354-9", "display": "Blood pressure panel with all children optional" },
+      { "code": "8867-4", "display": "Heart rate" },
+      { "code": "9279-1", "display": "Respiratory rate" },
+      { "code": "8310-5", "display": "Body temperature" },
+      { "code": "2708-6", "display": "Oxygen saturation in Arterial blood" },
+      { "code": "39156-5", "display": "Body mass index (BMI)" },
+      { "code": "59408-5", "display": "Oxygen saturation in Arterial blood by Pulse oximetry" },
+      { "code": "8480-6", "display": "Systolic blood pressure" },
+      { "code": "8462-4", "display": "Diastolic blood pressure" },
+      { "code": "718-7", "display": "Hemoglobin [Mass/volume] in Blood" },
+      { "code": "2339-0", "display": "Glucose [Mass/volume] in Blood" },
+      { "code": "55284-4", "display": "Blood pressure systolic and diastolic" },
+      { "code": "3141-9", "display": "Body weight Measured" },
+      { "code": "72166-2", "display": "Tobacco smoking status" },
+      { "code": "11506-3", "display": "Provider-unspecified Progress note" },
+      { "code": "4548-4", "display": "Hemoglobin A1c/Hemoglobin.total in Blood" },
+      { "code": "2093-3", "display": "Cholesterol [Mass/volume] in Serum or Plasma" },
+      { "code": "2571-8", "display": "Triglyceride [Mass/volume] in Serum or Plasma" },
+      { "code": "6690-2", "display": "Leukocytes [#/volume] in Blood by Automated count" },
+      { "code": "789-8", "display": "Erythrocytes [#/volume] in Blood by Automated count" },
+      { "code": "777-3", "display": "Platelets [#/volume] in Blood by Automated count" },
+      { "code": "1742-6", "display": "Alanine aminotransferase [Enzymatic activity/volume] in Serum or Plasma" },
+      { "code": "1920-8", "display": "Aspartate aminotransferase [Enzymatic activity/volume] in Serum or Plasma" },
+      { "code": "2160-0", "display": "Creatinine [Mass/volume] in Serum or Plasma" },
+      { "code": "3094-0", "display": "Urea nitrogen [Mass/volume] in Serum or Plasma" },
+      { "code": "2823-3", "display": "Potassium [Moles/volume] in Serum or Plasma" },
+      { "code": "2951-2", "display": "Sodium [Moles/volume] in Serum or Plasma" },
+      { "code": "14959-1", "display": "Microalbumin [Mass/volume] in Urine" },
+      { "code": "82810-3", "display": "Pregnancy status" }
+    ],
+    "http://snomed.info/sct": [
+      { "code": "27113001", "display": "Body weight" },
+      { "code": "50373000", "display": "Body height measure" },
+      { "code": "75367002", "display": "Blood pressure" },
+      { "code": "364075005", "display": "Heart rate" },
+      { "code": "86290005", "display": "Respiratory rate" },
+      { "code": "386725007", "display": "Body temperature" },
+      { "code": "431314004", "display": "SpO2 - Loss of oxygen in blood" },
+      { "code": "60621009", "display": "Body mass index" },
+      { "code": "271649006", "display": "Systolic blood pressure" },
+      { "code": "271650006", "display": "Diastolic blood pressure" },
+      { "code": "404684003", "display": "Clinical finding" },
+      { "code": "118228005", "display": "Functional finding" },
+      { "code": "250171008", "display": "Clinical history and observation findings" },
+      { "code": "363787002", "display": "Observable entity" },
+      { "code": "386661006", "display": "Fever" }
+    ]
+  },
+  "valueSets": {
+    "http://hl7.org/fhir/ValueSet/observation-codes": ["http://loinc.org"],
+    "http://hl7.org/fhir/ValueSet/body-site": ["http://snomed.info/sct"],
+    "http://hl7.org/fhir/ValueSet/observation-methods": ["http://snomed.info/sct"],
+    "http://hl7.org/fhir/ValueSet/clinical-findings": ["http://snomed.info/sct"],
+    "http://hl7.org/fhir/ValueSet/condition-code": ["http://snomed.info/sct"]
+  }
+}