OntoBoomOntoBoomHub
← Hub

@ontoboom/healthcare-lite

Lightweight clinical schema: patient, encounter, practitioner, observation, condition, medication, and care plan. Inspired by FHIR R5 but trimmed to the minimum agents need to reason over a single visit. NOT a HIPAA-compliant production schema and NOT for clinical decision-making — use as a starting point for non-PHI synthetic workflows.

14
Classes
20
Object properties
48
Data properties
0
Individuals

Connect this ontology

● Checking…
MCP endpoint
https://mcp.ontoboom.com/o/@ontoboom/healthcare-lite@0.1.0
{
  "mcpServers": {
    "ontoboom": {
      "url": "https://mcp.ontoboom.com/o/@ontoboom/healthcare-lite@0.1.0",
      "transport": "sse"
    }
  }
}

Two manifest-derived tools are exposed in this iteration:list_entities anddescribe_entity. More tools (find_relationship, enumerate_values) ship as followups.

README

@ontoboom/healthcare-lite

A trimmed-down clinical ontology covering the patient → encounter → outcome loop. Inspired by FHIR R5 but deliberately small.

WARNING — non-clinical use only. This schema is for AI agent experimentation against synthetic data. It does not implement HIPAA Privacy / Security Rule controls and must not be used to handle Protected Health Information (PHI) on a public Hub. For production clinical deployments, consult FHIR directly.

Coverage

  • Patient (demographics only — no PHI identifiers)
  • Practitioner (clinicians, with role)
  • Organization (clinic, hospital, payer)
  • Encounter (visit) with admission + discharge timestamps
  • Observation (vital signs, lab results, structured measurements)
  • Condition (problem-list entry with onset + status)
  • MedicationRequest + MedicationStatement
  • CarePlan + Goal
  • AllergyIntolerance

SHACL highlights

  • Patient.birthDate present, sex enumerated (male|female|other|unknown — pragmatic v1 set).
  • Observation.value paired with units; valueQuantity >= 0.
  • Encounter.status enumerated planned|in-progress|completed|cancelled.
  • Condition.clinicalStatus enumerated active|recurrence|relapse|inactive|remission|resolved.

Forking

For payer workflows, fork and extend with Claim / ExplanationOfBenefit. For chronic-disease management, extend CarePlan with structured Activity sub-entities.

Reviews

Sign in to review

No reviews yet · Be the first to review.

Sort: