bkaney

Review: BP-2026-03-quantity-preview Spec Branch

Analysis of the proposed quantity handling changes in HL7/FHIRPath branch BP-2026-03-quantity-preview, from the perspective of our Rust FHIRPath engine.

---

What We Think is Right

The bulk of the proposal is long overdue and we support it:

bkaney

#!/usr/bin/env bash
set -euo pipefail

# code-client: launch VS Code with per-client user-data-dir based on
# ~/projects/{client}/{project} hierarchy.

PROJECTS_ROOT="${PROJECTS_ROOT:-$HOME/projects}"
CODE_BIN="${CODE_BIN:-code}"

usage() {

bkaney

LessPrompt - All Modes Comparison

Generated on 2025-12-10 23:10:14

✅ Ollama is running with ministral-3:8b

This demo compares all optimization modes across test fixtures.

---

bkaney

{
  "resourceType" : "ImplementationGuide",
  "id": "example.fhir.package",
  "url": "http://example.com/fhir/package/ImplementationGuide/example.fhir.package",
  "version": "0.1.0",
  "name": "ExamplePackage",
  "title": "Example Package"
  "status": "draft",
  "packageId": "example.fhir.package",
  "fhirVersion": ["4.0.1"]

bkaney

{
  "resourceType": "Library",
  "id": "sql-on-fhir-example",
  "meta": {
    "versionId": "1",
    "lastUpdated": "2025-07-21T15:16:54.620668Z"
  },
  "status": "active",
  "type": {
    "coding": [

bkaney

Reporting/removing artifacts from the patient record. False diagnosis are billed and on your record for good without easily being able to have them removed

Wearables and personal devices are better. No change in hospitals and drs sharing information.

The vast heterogeniety in apps and lack of a consumer friendly one stop shop.

Coordination between payer and hospital systems are still severely lacking and billing is usually not explained for us mere mortals, just codes added

It's not linked between primary and secondary care settings very well

bkaney

[System Instructions]

I want you to act as a terminologist. Your task is to identify both lexical and
semantic mappings from {{source-codesystem}} to {{target-codesystem}}

[Context]
- Domain: Clinical Termiology
- Constraints: Use only {{source-codesystem}} to {{target-codesystem}} CodeSystems

bkaney

FHIR Canonical Resources and Packages (AI Draft)

1. Introduction

This specification defines how FHIR canonical resources and packages are:

1. Authored (i.e., created and maintained in Implementation Guides (IGs))
2. Assembled (Configured) ready for distribution for final systems by users
3. Executed (Runtime) to provide functionality

bkaney

{
  "name": "fhir-package-loader",
  "version": "0.7.0",
  "description": "JavaScript package for downloading and accessing FHIR definitions",
  "scripts": {
    "build": "tsc",
    "build:watch": "tsc -w",
    "test": "jest --coverage",
    "test:watch": "npm run test -- --watchAll",
    "coverage": "opener coverage/lcov-report/index.html",

bkaney

Logical: ViewDefinition
Title: "View Definition"
* select 0..* BackboneElement "The select stanza defines the actual content of the view itself"
  * name 1..1 string "Name of field produced in the output."
  * expression 1..1 string "FHIRPath expression, can include %constant"
  * forEach 0..1 BackboneElement "Expression unnest a new row for each item in the specified FHIRPath expression."
    * expression 1..1 string "FHIRPath expression for the parent path to select values from"
    * select 0..* contentReference #ViewDefinition.select "See select" "Nested select"

Instance:   PatientAddresses