← Back to catalogue
Published

Personal Health

vr.wm-per-007 · wm-per-007-personal-health

Represent one person's longitudinal health states, observations, risks, interventions, care intentions and evidence with strict identity, provenance, clinical-safety and privacy controls independent of storage or interface format.

World Models Society, people and institutions SOC.PER.HLTH

Bundle → Layer → Finding → Questions Filled

7 bundles · 16 layers · 32 findings · 96 questions

Subject, record and longitudinal boundary Identifies whose health context is represented and how distributed source records join without identity collapse.

Subject and record identity

Stable subject linkage and the identity of this longitudinal context.

Subject reference, identity assurance and match basis

Authoritative person reference, identifiers, assigners, match method, assurance, conflicts and manual-review state.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for subject reference, identity assurance and match basis? identity
  2. Which person, practitioner, organization, device, source and evidence establishes subject reference, identity assurance and match basis, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may subject reference, identity assurance and match basis be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Health-context identifier, custodian, controller and master bindings

Identity of the federated context plus source-system, custodian, controller, repository and portability bindings without universal ownership inference.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for health-context identifier, custodian, controller and master bindings? ownership
  2. Which person, practitioner, organization, device, source and evidence establishes health-context identifier, custodian, controller and master bindings, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may health-context identifier, custodian, controller and master bindings be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Assertion status and longitudinal time

How claims from different sources coexist, change and form a time-aware view.

Assertion kind, source, status, verification and contestation

Separates self-report, clinical assertion, direct observation, device output and algorithmic inference with verification, refutation and entered-in-error states.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for assertion kind, source, status, verification and contestation? provenance
  2. Which person, practitioner, organization, device, source and evidence establishes assertion kind, source, status, verification and contestation, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may assertion kind, source, status, verification and contestation be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Clinical event, effective, recorded, issued, observed and knowledge time

Distinct instants and intervals, precision, timezone, uncertainty, retrospective entry and correction lineage.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for clinical event, effective, recorded, issued, observed and knowledge time? temporal
  2. Which person, practitioner, organization, device, source and evidence establishes clinical event, effective, recorded, issued, observed and knowledge time, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may clinical event, effective, recorded, issued, observed and knowledge time be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation
Health state, risk and function Represents conditions, health concerns, risks and the person's functional state.

Conditions and problem list

Clinically asserted and self-reported health problems with course and evidence.

Condition, concern, diagnosis code and verification

Condition identity, category, terminology, evidence, clinical and verification status, onset and recorder or asserter.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for condition, concern, diagnosis code and verification? state
  2. Which person, practitioner, organization, device, source and evidence establishes condition, concern, diagnosis code and verification, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may condition, concern, diagnosis code and verification be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Severity, stage, course, remission, resolution and recurrence

Time-qualified course assertions, stages, body sites, episodes, remission, relapse and resolved state with explicit source.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for severity, stage, course, remission, resolution and recurrence? lifecycle
  2. Which person, practitioner, organization, device, source and evidence establishes severity, stage, course, remission, resolution and recurrence, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may severity, stage, course, remission, resolution and recurrence be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Risk, function and lived health

Risk estimates and physical, cognitive, mental and social functioning.

Risk factor, family history, prediction and prevention context

Observed and asserted factors, model or guideline references, probability horizon, uncertainty and prevention links without deterministic diagnosis.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for risk factor, family history, prediction and prevention context? measurement
  2. Which person, practitioner, organization, device, source and evidence establishes risk factor, family history, prediction and prevention context, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may risk factor, family history, prediction and prevention context be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Functional, cognitive, mental, social and quality-of-life status

Activities, participation, body functions, limitations, supports, instruments, self-report and clinician observation with ICF alignment.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for functional, cognitive, mental, social and quality-of-life status? state
  2. Which person, practitioner, organization, device, source and evidence establishes functional, cognitive, mental, social and quality-of-life status, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may functional, cognitive, mental, social and quality-of-life status be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation
Observations, diagnostics and evidence Represents measurements, results and their diagnostic context with sufficient semantics for safe interpretation.

Measurement and observation

Individual quantitative, qualitative and coded findings.

Observation code, value, unit, component and status

LOINC or other code, value form, UCUM and displayed unit, components, status, performer, device and derived-from references.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for observation code, value, unit, component and status? measurement
  2. Which person, practitioner, organization, device, source and evidence establishes observation code, value, unit, component and status, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may observation code, value, unit, component and status be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Method, body site, posture, context, reference range and interpretation

Collection and measurement conditions, body site, posture, fasting or other context, population-specific ranges, flags and interpretive authority.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for method, body site, posture, context, reference range and interpretation? evidence
  2. Which person, practitioner, organization, device, source and evidence establishes method, body site, posture, context, reference range and interpretation, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may method, body site, posture, context, reference range and interpretation be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Specimen, imaging and genomic references

Links high-volume diagnostic evidence while leaving its native master external.

Specimen collection, processing, accession and chain of custody

Specimen reference, type, collection site and time, container, processing, accession, adequacy and custody evidence.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for specimen collection, processing, accession and chain of custody? provenance
  2. Which person, practitioner, organization, device, source and evidence establishes specimen collection, processing, accession and chain of custody, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may specimen collection, processing, accession and chain of custody be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Imaging study, series, instance, report and genomic-result reference

DICOM study and report identifiers plus external genomic result references, access controls, digests and derived summary links.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for imaging study, series, instance, report and genomic-result reference? relationship
  2. Which person, practitioner, organization, device, source and evidence establishes imaging study, series, instance, report and genomic-result reference, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may imaging study, series, instance, report and genomic-result reference be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Diagnostic interpretation and uncertainty

Panels, reports, evidence links and explicit limits on meaning.

Diagnostic report, panel, conclusion, performer and finality

Report identity, grouped results, conclusion, interpreter, status, issued time, amendment and superseded versions.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for diagnostic report, panel, conclusion, performer and finality? evidence
  2. Which person, practitioner, organization, device, source and evidence establishes diagnostic report, panel, conclusion, performer and finality, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may diagnostic report, panel, conclusion, performer and finality be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Evidence link, uncertainty, detection limit, data absent and disagreement

Supporting and contradicting evidence, measurement uncertainty, detection bounds, absence reason, conflicting interpretation and unresolved state.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for evidence link, uncertainty, detection limit, data absent and disagreement? quality
  2. Which person, practitioner, organization, device, source and evidence establishes evidence link, uncertainty, detection limit, data absent and disagreement, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may evidence link, uncertainty, detection limit, data absent and disagreement be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation
Safety, medication, immunization and procedures Captures standing safety risks and clinically relevant interventions.

Allergy, intolerance and adverse reaction

Substances, manifestations, exposure and confidence needed for safety decisions.

Allergy or intolerance substance, category and reaction

Coded agent or substance, allergy versus intolerance category, manifestations, exposure route, onset, severity and evidence.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for allergy or intolerance substance, category and reaction? state
  2. Which person, practitioner, organization, device, source and evidence establishes allergy or intolerance substance, category and reaction, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may allergy or intolerance substance, category and reaction be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Allergy verification, criticality, last occurrence and refutation

Clinical and verification status, criticality, recorder, confirmer, last exposure or reaction and refuted or entered-in-error history.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for allergy verification, criticality, last occurrence and refutation? validation
  2. Which person, practitioner, organization, device, source and evidence establishes allergy verification, criticality, last occurrence and refutation, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may allergy verification, criticality, last occurrence and refutation be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Medication and immunization

Intent, supply, use and administration history for medicines and vaccines.

Medication request, dispense, administration and statement reconciliation

Product code, intent, dose, route, schedule, indication, prescriber, supply, actual use, adherence and source discrepancies.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for medication request, dispense, administration and statement reconciliation? process
  2. Which person, practitioner, organization, device, source and evidence establishes medication request, dispense, administration and statement reconciliation, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may medication request, dispense, administration and statement reconciliation be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Immunization dose, product, lot, site, reaction and validity

Vaccine, disease target, dose number, lot, site, route, performer, reaction, status, source and schedule or validity interpretation.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for immunization dose, product, lot, site, reaction and validity? event
  2. Which person, practitioner, organization, device, source and evidence establishes immunization dose, product, lot, site, reaction and validity, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may immunization dose, product, lot, site, reaction and validity be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Procedures, devices and outcomes

Performed or planned interventions and implanted or assistive devices.

Procedure or treatment status, performer, body site, reason and outcome

Procedure identity, code, occurrence, status, indication, performer, body site, complications, outcome and report reference.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for procedure or treatment status, performer, body site, reason and outcome? event
  2. Which person, practitioner, organization, device, source and evidence establishes procedure or treatment status, performer, body site, reason and outcome, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may procedure or treatment status, performer, body site, reason and outcome be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Implant or assistive device, UDI, use period and safety reference

External device identity, unique device identifier, implant or use interval, status, owner, safety notice and removal reference.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for implant or assistive device, udi, use period and safety reference? relationship
  2. Which person, practitioner, organization, device, source and evidence establishes implant or assistive device, udi, use period and safety reference, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may implant or assistive device, udi, use period and safety reference be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation
Encounters, care plans and coordination Links health assertions to care contacts, responsible teams, intentions, goals and follow-up.

Encounters, participants and context

Contacts with care settings and the actors and reasons that frame them.

Encounter class, type, reason, period, location and disposition

External encounter reference, class, care setting, reason, priority, start and end, location, hospitalization context and disposition.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for encounter class, type, reason, period, location and disposition? event
  2. Which person, practitioner, organization, device, source and evidence establishes encounter class, type, reason, period, location and disposition, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may encounter class, type, reason, period, location and disposition be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Practitioner, organization, care-team role and responsibility

External provider and team identities, encounter or plan role, responsibility interval, communication route and source.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for practitioner, organization, care-team role and responsibility? relationship
  2. Which person, practitioner, organization, device, source and evidence establishes practitioner, organization, care-team role and responsibility, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may practitioner, organization, care-team role and responsibility be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Plans, goals, referrals and follow-up

Agreed or proposed future care and its responsible actors.

Care plan, goal, activity, priority, owner and progress

Plan and goal identities, intent, status, targets, activities, responsible parties, progress evidence, review and replacement lineage.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for care plan, goal, activity, priority, owner and progress? process
  2. Which person, practitioner, organization, device, source and evidence establishes care plan, goal, activity, priority, owner and progress, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may care plan, goal, activity, priority, owner and progress be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Appointment, referral, service request, follow-up and patient instruction

External request and appointment references, recipient, urgency, reason, due time, completion status and versioned instructions.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for appointment, referral, service request, follow-up and patient instruction? relationship
  2. Which person, practitioner, organization, device, source and evidence establishes appointment, referral, service request, follow-up and patient instruction, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may appointment, referral, service request, follow-up and patient instruction be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation
Provenance, consent, privacy and retention Makes every material assertion attributable and governs highly sensitive access and lifecycle.

Provenance, consent and directives

Source lineage and the person's or lawful representative's choices.

Author, recorder, asserter, performer, source, derivation and signature

Attributable roles, source record, import path, transformations, signatures, digests and revision lineage for each assertion.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for author, recorder, asserter, performer, source, derivation and signature? provenance
  2. Which person, practitioner, organization, device, source and evidence establishes author, recorder, asserter, performer, source, derivation and signature, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may author, recorder, asserter, performer, source, derivation and signature be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Consent or directive purpose, recipient, data scope, validity and revocation

Legal-basis and consent references, represented party, purposes, recipients, permitted data, exclusions, interval and withdrawal effect.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for consent or directive purpose, recipient, data scope, validity and revocation? authority
  2. Which person, practitioner, organization, device, source and evidence establishes consent or directive purpose, recipient, data scope, validity and revocation, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may consent or directive purpose, recipient, data scope, validity and revocation be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Access, correction, emergency and retention

Field-sensitive disclosure, person rights, break-glass use and durable evidence.

Confidentiality, access, minimum disclosure, emergency use and audit

Sensitivity labels, audience, purpose, minimum view, emergency authority, expiry, notification, post-review and immutable access log.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for confidentiality, access, minimum disclosure, emergency use and audit? access
  2. Which person, practitioner, organization, device, source and evidence establishes confidentiality, access, minimum disclosure, emergency use and audit, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may confidentiality, access, minimum disclosure, emergency use and audit be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Access right, correction, amendment, restriction, retention, hold and deletion

Request and decision history, contested data, source correction, appended amendment, retention class, legal hold, disposition and tombstone.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for access right, correction, amendment, restriction, retention, hold and deletion? retention
  2. Which person, practitioner, organization, device, source and evidence establishes access right, correction, amendment, restriction, retention, hold and deletion, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may access right, correction, amendment, restriction, retention, hold and deletion be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation
Interoperability, summaries, validation and agent operations Controls terminology, summary projections and safe automated maintenance.

Terminology and summary projections

Versioned mappings and purpose-specific portable views.

FHIR resource, IPS, emergency, self and research view

Source and target profile, section inclusion, omissions, confidentiality, expiry, digest and non-round-trip declaration for each projection.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for fhir resource, ips, emergency, self and research view? interoperability
  2. Which person, practitioner, organization, device, source and evidence establishes fhir resource, ips, emergency, self and research view, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may fhir resource, ips, emergency, self and research view be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Terminology, classification, unit, version, map and licence

Code system URI, release or edition, code, display, inactive state, map rule, equivalence, UCUM unit and licence constraints.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for terminology, classification, unit, version, map and licence? classification
  2. Which person, practitioner, organization, device, source and evidence establishes terminology, classification, unit, version, map and licence, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may terminology, classification, unit, version, map and licence be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Clinical safety and agent control

Authorized operations, clinical review, validation, concurrency and recovery.

Agent authority, clinical review, purpose, preconditions and non-advice

Classifies reads, imports, proposals, corrections, disclosures and disposition as autonomous, propose, confirm or forbidden and blocks unsupervised clinical conclusions.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for agent authority, clinical review, purpose, preconditions and non-advice? security
  2. Which person, practitioner, organization, device, source and evidence establishes agent authority, clinical review, purpose, preconditions and non-advice, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may agent authority, clinical review, purpose, preconditions and non-advice be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Pre-write and post-write validation, conflict, concurrency, rollback and audit

Identity, terminology, unit, status, temporal, provenance, consent, stale-head and safety checks with immutable before and after evidence.

  1. What exact values, codes, references, qualifiers and explicit unknown or data-absent reasons must be recorded for pre-write and post-write validation, conflict, concurrency, rollback and audit? validation
  2. Which person, practitioner, organization, device, source and evidence establishes pre-write and post-write validation, conflict, concurrency, rollback and audit, at what clinical, observation and knowledge time, and with what confidence? evidence
  3. How may pre-write and post-write validation, conflict, concurrency, rollback and audit be clinically validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring record lifecycle? validation

Classifiers Filled

Family
World Models
Category
Society, people and institutions
Entry kind
entity
Navigation path
NAV.SOC.PER.HLTH
Domain
SOC.PER.HLTH
Industry
Cross-industry
Tags
personalhealthsoc.per.hlth
Also called
B10

What it is Filled

Owns the person-grain health context, subject and source bindings, assertion kinds and time, conditions, risks, function, observations, diagnostic interpretations, allergies, medications, immunizations, procedures, encounter and plan references, provenance, consent, access, correction, retention and summary projections. External systems own people, providers, organizations, devices, products, appointments, encounters, specimens, images, claims, research studies, public-health reports, genomics, consents and source evidence records.

In scope

  • Verified subject and context identity, source mastering, assertion status, longitudinal time, provenance and reconciliation
  • Conditions, risks, function, observations, diagnostic evidence, allergies, medicines, immunizations, procedures, devices, encounters, teams, plans and goals
  • Consent, privacy, emergency access, correction, retention, terminology, interoperable summaries, validation and safe agent operations

Out of scope

  • Provider operations, scheduling, billing, insurance claims, population surveillance, research-study management, raw genomics, raw imaging and medical-device implementation
  • Universal clinical guidelines, diagnosis or treatment recommendations, professional licensure decisions and claims of medical correctness without accountable review
  • Universal legal ownership, consent, access, retention or emergency rules and any silent replacement of source-system records

Why it exists Filled

Represent one person's longitudinal health states, observations, risks, interventions, care intentions and evidence with strict identity, provenance, clinical-safety and privacy controls independent of storage or interface format.

Distinguishing features Filled

  • Health information about one person across sources, not a provider's operational record.
  • Each assertion keeps its kind, time and source, so self-reported and clinician-recorded data stay distinct.
  • Consent, access and correction are part of the record.
  • Differs from population health data, which is aggregated.

What robots and AI may and may not do Filled

Must not

  • Diagnose or prescribe.
  • Share records without the person's consent or a lawful basis.
  • Alter clinical entries; corrections go through the source.
  • Use health data for advertising, insurance pricing or employment decisions.
  • Hide uncertainty or the age of data.

Only with a human decision

  • Clinical decisions.
  • Sharing data with new recipients.
  • Emergency access overrides.

May

  • Help the person collect and organize their own health records.
  • Summarize records with their sources and dates.
  • Remind the person of plans, medications and appointments they recorded.
  • Flag inconsistencies such as duplicate medications for review.

Moral aspects Filled

  • Health data is among the most sensitive personal data.
  • People have a right to access and correct their records.
  • Errors can lead to dangerous treatment decisions.
  • Stigma can follow disclosure of mental health, sexual health or genetic data.

Who is affected

  • The person themselves
  • Family and carers
  • Clinicians relying on the record

Owners Filled

Steward

Dimension identity, owner, health-data steward, clinical safety authority, privacy steward and namespace

Roles

Person or lawful representative
Exercise lawful access, consent, portability, correction and preference rights and contribute self-reported facts.
Clinical professional
Author and verify clinical assertions, interpret results and approve care changes within professional scope.
Health-data steward
Maintain subject linkage, source maps, terminology pins, provenance and longitudinal reconciliation.
Custodian or controller
Apply legal basis, access, security, retention, breach and disclosure duties for the held records.
Laboratory, imaging, pharmacy or device source
Master its source records, identifiers, status, quality and correction route.
Privacy and consent steward
Evaluate purpose, minimum disclosure, consent or other legal basis, restrictions and emergency use.
Clinical safety reviewer
Review identity, medicine, allergy, result and decision-support hazards and corrective action.
Independent auditor
Review access, provenance, reconciliation, corrections and disposition without changing clinical truth.

Links to other meta-models Filled

references

  • Person, Identity, Provider, Organization, Device, Product, Encounter, Appointment, Specimen, Imaging, Genomics, Claim, Research, Public Health, Consent, Incident and Evidence models - Connect the personal health context to externally mastered subjects, actors, events, artifacts and legal records without lifecycle duplication.

aligned

  • HL7 FHIR Release 5 - Project source-qualified person health assertions to clinical resource profiles while preserving identity, status, time and provenance.
  • HL7 International Patient Summary - Produce a minimal clinically relevant cross-border or unscheduled-care summary as a purpose-bound projection.
  • WHO ICD-11, SNOMED CT and LOINC - Reference versioned condition, clinical concept, observation and document identifiers without copying terminology masters.
  • DICOM, ICF and UCUM - Reference imaging objects, functioning classifications and computable measurement units with explicit versions and mapping loss.
  • W3C PROV-O - Preserve author, performer, source, derivation, transformation and revision provenance across federated health records.

neighbor

  • Person and Identity Register - The person model owns identity and demographics; Personal Health stores verified subject references, match evidence and corrections but never remasters the person.
  • Health-care Delivery, Encounter and Appointment - Care delivery owns services, resources, workflow and scheduling; Personal Health retains clinically relevant references and resulting assertions at person grain.
  • Public Health and Research - Population surveillance and studies own cohort, protocol and reporting semantics; only authorized person-grain participation or disclosure references live here.
  • Device, Imaging, Specimen and Genomics - Native payloads and lifecycles remain in specialist masters; this model holds identifiers, clinically relevant summaries, provenance and access references.
  • Insurance, Coverage and Claim - Financial eligibility and adjudication are external; they may reference health evidence but never define clinical truth.
  • Consent, Access and Legal Policy - This model records health-specific policy and consent bindings and their effects, while authorization engines and jurisdictional legal determinations remain external.

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Authoritative master-system identifier for the person-grain health assertion, qualified by source and subject.
  • Governed globally resolvable assertion identifier with explicit source-record binding.
  • Adopting-Dimension UUID or ULID when no authoritative external identifier exists.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Filled

  • A personal health record is tied to one person and holds dated assertions with source and kind.
  • It is confused with a provider's electronic health record and with fitness app data.

Capabilities and actions required Filled

  • Register personal health context: Create the subject linkage, context identity, custodianship and source-master map.
  • Ingest health assertion: Append a source-qualified clinical, self-reported, device-observed or inferred assertion without changing its authority class.
  • Reconcile subject and source: Compare identifiers, masters and competing source statements and append match, non-match or unresolved evidence.
  • Record condition or health state: Append a condition, concern, risk or functional-state assertion with verification and course.
  • Record observation or result: Append a measurement, panel or diagnostic report with units, method, context and interpretation.
  • Reconcile medication and allergy safety: Compare allergy and medication sources and record agreement, discrepancy, verification or refutation.
  • Record intervention or immunization: Append a procedure, treatment, immunization or device-use event with performer, reason and outcome.
  • Update care plan and goal: Append a proposed, agreed, active, completed or replaced plan and its goals, activities and progress evidence.
  • Issue purpose-bound health summary: Create an IPS, emergency, self or research projection with explicit omissions and expiry.
  • Grant, revoke or exercise emergency access: Record scoped access authority or one-time emergency use with expiry, notification and post-review.
  • Correct or supersede health assertion: Append correction, refutation, entered-in-error or source amendment while preserving prior clinical context.
  • Retain, restrict, export or dispose: Apply retention, legal hold, portability and disposition decisions per artifact and jurisdiction profile.

Hazards and failure modes required Filled

  • Privacy breach of sensitive data.
  • Wrong-patient matching.
  • Outdated allergy or medication lists causing harm.
  • Misreading self-reported data as clinical findings.

Standards and interfaces required Filled

  • HL7 FHIR International Patient Summary (IPS).
  • SNOMED CT, LOINC and ICD-11.
  • IHE profiles for cross-enterprise document sharing (XDS).
  • ISO/TS 22220 for subject of care identification.

Context of use required Filled

  • The GDPR supplies an EU privacy profile and does not create universal global health-record ownership, consent, retention or emergency-access rules.
  • FHIR and IPS are interoperability standards and do not by themselves determine clinical truth, medical necessity, legal authority or record custody.
  • ICD, SNOMED CT, LOINC, DICOM, ICF and UCUM have separate governance, release and licence conditions that adopting Dimensions must verify.

Sources Filled

  1. FHIR Release 5 - Health Level Seven International
  2. International Patient Summary Implementation Guide - Health Level Seven International
  3. ICD-11 for Mortality and Morbidity Statistics - World Health Organization
  4. SNOMED CT Release File Specification - SNOMED International
  5. LOINC Users' Guide - Regenstrief Institute
  6. DICOM Standard Current Edition - DICOM Standards Committee
  7. Unified Code for Units of Measure - Regenstrief Institute
  8. PROV-O: The PROV Ontology - World Wide Web Consortium
  9. International Classification of Functioning, Disability and Health - World Health Organization
  10. General Data Protection Regulation - European Union
  11. Date and Time on the Internet: Timestamps - Internet Engineering Task Force

Open questions

  • Develop jurisdiction profiles for consent, incapacity, guardian authority, emergency access, retention, source correction and public-health disclosure.
  • Approve model identifiers and relation cardinalities for persons, providers, organizations, encounters, devices, products, specimens, imaging, genomics, claims, research, consent, incidents and evidence.
  • Create specialist profiles for paediatric, reproductive, mental, genetic, disability, occupational, travel, dental, veterinary-adjacent household and remote-monitoring contexts where appropriate.
  • Create deterministic fixtures for wrong-patient prevention, source disagreement, unit conversion, terminology inactivation, allergy refutation, medication reconciliation, corrected reports and emergency access.
  • Validate certified FHIR and IPS projections plus terminology, imaging, function and unit mappings with explicit disclosure, licence, loss and round-trip tests.
  • No independent Claude or Grok result was available; this source-grounded Codex fallback requires later clinical and external review before canonical promotion.
  • National clinical, privacy, retention, consent, emergency, public-health, paediatric, reproductive-health, mental-health, genetic and incapacity rules require jurisdiction-specific profiles.
  • Insurance, claims, provider operations, public health, research, genomics, medical-device payloads and care-delivery workflows remain external.
  • The frozen relation ledger contains no approved WM-PER-007 dependency rows; composition targets remain draft until registry review.
  • Certified FHIR, IPS, ICD-11, SNOMED CT, LOINC, DICOM, ICF and UCUM crosswalks, licence review and clinical conformance fixtures remain future work.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-per-007-personal-health/spec.yaml, ver-cy/world-models/card-supplements/wm-per-007-personal-health.json