← Back to catalogue
Generated draft

digital health

vr.tr.digital-health · thing-q5276090

Give an agent a durable, checkable way to recognise a digital health, record what state it is in, and decide what may be done with it.

Thing Registry Cross-cutting context XCT.QLT

Generated draft, first pass

This model was drafted by rule from what the registry knows about the thing. It proposes which bundles a real model will need and which questions research must answer. It is not researched and no sentence in it is sourced.

Generator: vr.draft.v3

Bundle → Layer → Finding → Questions Derived, awaiting review

5 bundles · 10 layers · 12 findings · 32 questions

Identity, naming and classification How an agent tells one digital health from another, and a digital health from things that resemble it.

Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.

Names and identifiers

The names this thing goes by and the identifiers that survive translation and time.

Preferred name, aliases and local names

Which name to use, which names mean the same thing, and which merely sound similar.

  1. What identifies and describes the name of a digital health, and in what units or vocabulary? definition
  2. Who or what asserted this about the name of a digital health, by which method, and when was it true? provenance
  3. What may an agent decide or do once the name of a digital health is known, and what must it refuse? action

Stable identifiers and external keys

Identifiers that keep pointing at this kind of thing across systems and languages.

  1. What identifies and describes an identifier for a digital health, and in what units or vocabulary? definition
  2. Who or what asserted this about an identifier for a digital health, by which method, and when was it true? provenance
  3. What may an agent decide or do once an identifier for a digital health is known, and what must it refuse? action

Classification and granularity

Where a digital health sits among kinds, and how finely a task needs to cut it.

Kind, parents and neighbouring kinds

The classes this thing belongs to and the ones it is next to.

  1. What identifies and describes the kind of a digital health, and in what units or vocabulary? definition
  2. Who or what asserted this about the kind of a digital health, by which method, and when was it true? provenance
  3. What may an agent decide or do once the kind of a digital health is known, and what must it refuse? action

Distinguishing features

What separates a digital health from the things most often confused with it.

  1. What identifies and describes what distinguishes a digital health, and in what units or vocabulary? definition
  2. Who or what asserted this about what distinguishes a digital health, by which method, and when was it true? provenance
  3. What may an agent decide or do once what distinguishes a digital health is known, and what must it refuse? action
State and lifecycle The states a digital health passes through and the events that move it between them.

Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.

Lifecycle stages

From coming into existence to ceasing to be one of these.

Stages and transitions

The stages worth naming and what moves a digital health between them.

  1. What identifies and describes the lifecycle of a digital health, and in what units or vocabulary? definition
  2. Who or what asserted this about the lifecycle of a digital health, by which method, and when was it true? provenance
  3. What may an agent decide or do once the lifecycle of a digital health is known, and what must it refuse? action

Observations and current status

What is observed about a digital health, how often and by whom.

Observation record

How an observation of a digital health is recorded so that it can be superseded rather than overwritten.

  1. What identifies and describes an observation of a digital health, and in what units or vocabulary? definition
  2. Who or what asserted this about an observation of a digital health, by which method, and when was it true? provenance
  3. What may an agent decide or do once an observation of a digital health is known, and what must it refuse? action
Definitions and who holds them What digital health is taken to mean, and by whom.

When a field disagrees about a concept, the disagreement is the content. A model that picks one definition silently destroys the information.

Competing definitions

The main readings and the traditions behind them.

Definitions and their holders

Each definition with the school or body that holds it.

  1. Which definitions of digital health are in use, and which tradition or body holds each? definition
  2. What turns on the difference between them in practice? boundary

Operationalisation

How it is measured or applied when it has to be.

Measures and proxies

Instruments and indicators used to stand in for it.

  1. How is digital health operationalised or measured in practice, and by what instrument? measurement
  2. What does that operationalisation leave out, and when does that matter? boundary
Instances, use and consequence What counts as an instance of digital health and what follows from calling something that.

Applying a concept is an act with consequences, so a model must say what the label licenses and what it does not.

What counts as an instance

Clear cases, borderline cases and non-cases.

Tests for an instance

What would settle whether something falls under it.

  1. What would settle whether something is an instance of digital health? boundary
  2. Which borderline cases are argued about, and on what grounds? definition

Consequence of application

Rights, duties or decisions that follow from the label.

What the label licenses

What an agent may do once something is classified this way.

  1. What follows practically once something is treated as digital health? action
  2. What must an agent not infer from the label alone? action
Provenance, evidence and time Where every claim about a digital health came from and when it held.

A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.

Source and authority

Who said it, on what evidence, and how strongly.

Claim provenance and confidence

The authority behind each claim about a digital health and how confident it is.

  1. What identifies and describes a claim about a digital health, and in what units or vocabulary? definition
  2. Who or what asserted this about a claim about a digital health, by which method, and when was it true? provenance
  3. What may an agent decide or do once a claim about a digital health is known, and what must it refuse? action

Time, versions and supersession

When a claim was true, when it was learnt, and what replaced it.

Validity period and supersession

How an old claim about a digital health is retired without being erased.

  1. What identifies and describes the validity of a claim about a digital health, and in what units or vocabulary? definition
  2. Who or what asserted this about the validity of a claim about a digital health, by which method, and when was it true? provenance
  3. What may an agent decide or do once the validity of a claim about a digital health is known, and what must it refuse? action

Classifiers Filled

Family
Thing Registry
Category
Cross-cutting context
Entry kind
abstract concept
Plane
XCT
Domain
XCT.QLT
Other names and narrower kinds
Digital Health Record Adoption in African Hospitals, Digital medicine, digital health and medical technologies

What it is Derived, awaiting review

A cross-cutting notion registered under XCT.QLT. The registry names it; this draft has not been given a definition yet.

Why it exists Derived, awaiting review

Give an agent a durable, checkable way to recognise a digital health, record what state it is in, and decide what may be done with it.

Distinguishing features Derived, awaiting review

  • Names folded into this entry, which a task may need to split apart again: Digital Health Record Adoption in African Hospitals, Digital medicine, digital health and medical technologies.
  • 3 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.
  • Described in 14 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is.

What robots and AI may and may not do Derived, awaiting review

May

  • observe it, measure it, record its state

Moral aspects Missing, in the backlog

Not described yet. This gap is in the card backlog.

Owners Missing, in the backlog

Not described yet. This gap is in the card backlog.

Links to other meta-models Derived, awaiting review

related

  • Digital Health Record Adoption in African Hospitals - covers: Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.
  • Digital medicine - covers: Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.
  • digital health and medical technologies - covers: Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.

What else AI and robots need to interact with it Incomplete

Identity and identifiers required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Direct properties not applicable Not applicable

  • Made of: an abstraction with no physical instance
  • Does nothing on its own; everything it does, something else did to it.
  • These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing.

Recognition optional Derived, awaiting review

  • Nothing to see. What is recognised is an instance of it, and which instances count is exactly what is argued about.

Capabilities and actions required Derived, awaiting review

  • observed and measured

Hazards and failure modes required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Standards and interfaces required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Context of use required Derived, awaiting review

  • Described in 14 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 3 finer distinctions are held inside this entry as names rather than as separate models.

Sources Missing, in the backlog

Not described yet. This gap is in the card backlog.

Open questions

  • Which of the bundles below does a real task actually need, and which are ceremony?
  • What does this thing have that the facets do not capture at all?
  • Which neighbouring kind is most often confused with a digital health, and on what evidence are they told apart?
  • What may an agent decide or do once the name of a digital health is known, and what must it refuse?
  • What may an agent decide or do once an identifier for a digital health is known, and what must it refuse?
  • What may an agent decide or do once the kind of a digital health is known, and what must it refuse?

Machine files

Provenance

thing registry, generated draft (pass 1) · not researched

Built from: models/draft_model.php, wikidata

Generated by rule from registry facets. No source was read; every derived section awaits the research pass.