Brian Kaney 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.

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

FHIR Canonical Resources and Packages (AI Draft)

1. Introduction

This specification defines how FHIR canonical resources and packages are:

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

Internal

Convert back to use sushi (the longer we wait, the more difficult it will be)
- Create a branch off master where FSH was removed (e.g. master-fsh)
- Work on parity with IG Publisher in this branch
- Promote master-fsh to master

Issues

Add support to definitional resource types that are not currently canonical in R4:
- In the definitional resource:
Add extensions: canonical-url, canonical-version (these already exist as: valueUri, valueString)

Background, this configuration --

- http://artifacts.org
  server-a-1
  
- http://artifacts.org
  server-a-2
  
- http://artifacts.org/ValueSet

	{
	"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"]

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

	[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

	{
	"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",

	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