{ "model": { "rank": 6126, "code": "thing-q79785", "model_id": "vr.tr.electrocardiography", "name": "electrocardiography", "purpose": "Enable an AI agent to recognise an electrocardiography procedure, assess whether its recording and interpretation are usable, and identify appropriate next actions within its authority.", "family": "Thing Registry", "category": "Activities and processes", "status": "research-draft", "kind": "thing", "plane": "ACT", "domain": "ACT.ACT", "industry": "", "version": "", "url": "/models/thing/q79785/", "tier": 2, "score": 62, "payload": { "layer": "wikidata", "aliases": [ "vectorcardiography", "body surface potential mapping", "veterinary electrocardiography", "Fetal echocardiography", "fetal electrocardiography" ], "aliasCount": 5, "merged": 5, "knownIn": 62, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q79785", "url": "https://www.wikidata.org/wiki/Q79785", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T11:40:49Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.0030328, "turns": 1, "seconds": 36.2, "error": null }, "codex": { "seconds": 80.2, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a07baa-8a50-7a40-890c-19d247b43e75\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: electrocardiography\nRegistry id: vr.tr.electrocardiography\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this " } } }, "metaModel": { "id": "THING-Q79785", "registryId": "vr.tr.electrocardiography", "name": "electrocardiography", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q79785/", "model": { "registry_id": "vr.tr.electrocardiography", "name": "electrocardiography", "purpose": "Enable an AI agent to recognise an electrocardiography procedure, assess whether its recording and interpretation are usable, and identify appropriate next actions within its authority.", "definition": "Electrocardiography is the recording and interpretation of the heart's time-varying surface potentials, produced by myocardial depolarization and repolarization, as a diagnostic and monitoring method.", "scope_statement": "This model owns electrocardiography as an activity that acquires, represents and interprets cardiac electrical potential differences through body-surface electrodes, including its purpose, acquisition conditions, signal quality, results and procedural disposition.", "in_scope": [ "The indication, intended question and acquisition mode of an electrocardiography procedure", "Electrode placement, lead configuration, recording duration and acquisition settings", "Waveform identity, technical quality, artefacts and limitations", "Electrocardiographic measurements, observations and attributed interpretations", "Review, comparison, repeat acquisition and communication of procedure results" ], "out_of_scope": [ "The patient's complete longitudinal health record and definitive disease diagnoses", "Echocardiography and other cardiac imaging procedures", "Intracardiac electrophysiology studies and invasive electrical mapping", "The complete exercise stress test or ambulatory monitoring programme surrounding an ECG acquisition", "ECG device manufacturing, maintenance and inventory management", "Treatment delivery, including medication administration, cardioversion and pacing" ], "distinguishing_features": [ "The procedure measures electrical potential differences using body-surface electrodes; a pulse waveform derived optically is photoplethysmography rather than electrocardiography.", "Its primary recorded evidence is voltage over time in identified leads; anatomical images or ultrasound-derived motion belong to cardiac imaging.", "Lead identity describes an electrical view and is not interchangeable with electrode identity or electrode count.", "A rhythm strip, reduced-lead wearable recording and standard 12-lead acquisition must remain distinguishable because they provide different electrical views.", "The procedure records cardiac electrical activity; electrical stimulation or shock delivery is a separate intervention." ], "characteristics": [ { "name": "Clinical question", "kind": "category", "unit_or_values": "Rhythm assessment, symptom investigation, interval assessment, surveillance, or another stated purpose", "why_it_matters": "Usability depends on whether the acquisition can answer the intended question." }, { "name": "Acquisition mode", "kind": "category", "unit_or_values": "Resting acquisition, rhythm strip, ambulatory segment, exercise-associated acquisition, or another specified mode", "why_it_matters": "Recording context changes what can be inferred from the observed interval." }, { "name": "Lead configuration", "kind": "category", "unit_or_values": "Named lead set, electrode locations, and any modified or derived leads", "why_it_matters": "Electrical views determine which waveform comparisons and interpretations are supported." }, { "name": "Recording duration", "kind": "measurement", "unit_or_values": "Seconds, minutes or hours, with interruptions identified", "why_it_matters": "A short observation cannot establish that an intermittent event never occurs." }, { "name": "Acquisition and display settings", "kind": "measurement", "unit_or_values": "Sampling rate in Hz, displayed speed in mm/s and gain in mm/mV, where applicable", "why_it_matters": "Timing and amplitude measurements require known acquisition or display settings." }, { "name": "Signal processing", "kind": "category", "unit_or_values": "Applied filters, resampling, averaging, lead derivation and unknown processing", "why_it_matters": "Processing may change waveform appearance and the reliability of measurements." }, { "name": "Technical usability", "kind": "state", "unit_or_values": "Not assessed, usable for stated question, usable with limitations, or unusable", "why_it_matters": "Technical adequacy must be judged against the intended use." }, { "name": "Measured ECG features", "kind": "measurement", "unit_or_values": "Rate in beats/min, intervals in ms, amplitudes in mV and axes in degrees, each with method and uncertainty", "why_it_matters": "Measurements need their lead, segment and method to remain interpretable." }, { "name": "Interpretation status", "kind": "state", "unit_or_values": "Uninterpreted, automated preliminary, human preliminary, reviewed, amended or indeterminate", "why_it_matters": "An algorithmic statement and a reviewed clinical interpretation carry different authority." }, { "name": "Associated clinical events", "kind": "relation", "unit_or_values": "Links to symptoms, exercise stages, interventions and prior ECG procedures with their times", "why_it_matters": "Temporal association supports contextual assessment without establishing causation." } ], "affordances": [ "Determine whether the recorded lead set, duration and conditions fit the stated clinical question.", "Identify technical limitations and propose targeted checks or repeat acquisition for authorised staff.", "Measure or extract ECG features while preserving the waveform segment, method and uncertainty.", "Compare compatible current and prior recordings while accounting for lead and acquisition differences.", "Distinguish automated observations from reviewed interpretations and route unresolved results for review.", "Track communication and acknowledgement of findings under an applicable clinical workflow." ] }, "sources": [ { "id": "aha-ecg-standardization", "title": "Recommendations for the Standardization and Interpretation of the Electrocardiogram", "url": "https://www.ahajournals.org/doi/10.1161/CIRCULATIONAHA.106.180200", "what_it_supports": "Clinical definition of ECG as surface recording of cardiac electrical activity; lead systems and measurement conventions used in practice.", "url_status": "blocked" } ], "structure": { "bundles": [ { "id": "electrocardiographic-purpose", "name": "Electrocardiographic purpose", "description": "The clinical question and observation context that make this ECG procedure meaningful.", "rationale": "An ECG can be technically sound yet inadequate for the question that prompted it.", "layers": [ { "id": "indication-and-question", "name": "Indication and question", "description": "Why this recording is being obtained and what it is intended to establish.", "findings": [ { "id": "intended-electrical-assessment", "name": "Intended electrical assessment", "description": "The stated reason for acquisition and the electrical features or events being sought.", "questions": [ { "text": "What symptom, observation or monitoring need prompted this ECG?", "kind": "provenance", "id": "intended-electrical-assessment-q01" }, { "text": "What question is this acquisition intended to answer, and what would remain unanswered?", "kind": "boundary", "id": "intended-electrical-assessment-q02" } ] } ] }, { "id": "observation-context", "name": "Observation context", "description": "The patient's recorded circumstances during the acquisition.", "findings": [ { "id": "symptoms-and-recording-conditions", "name": "Symptoms and recording conditions", "description": "The timing of symptoms and relevant conditions such as posture, movement or exercise.", "questions": [ { "text": "Was the recording obtained during the reported event, before it or after it, and how certain is that timing?", "kind": "measurement", "id": "symptoms-and-recording-conditions-q01" }, { "text": "What posture, activity, symptoms and relevant interventions were documented during acquisition?", "kind": "provenance", "id": "symptoms-and-recording-conditions-q02" } ] } ] } ] }, { "id": "lead-and-acquisition-design", "name": "Lead and acquisition design", "description": "The electrical views, observation window and settings used to produce the recording.", "rationale": "Lead geometry and acquisition settings determine which electrical evidence the procedure actually captures.", "layers": [ { "id": "electrodes-and-leads", "name": "Electrodes and leads", "description": "The relationship between physical electrode placement and recorded electrical views.", "findings": [ { "id": "actual-lead-configuration", "name": "Actual lead configuration", "description": "The acquired lead set, placement deviations and distinction between measured and derived signals.", "questions": [ { "text": "Which leads were recorded, and which were reconstructed or derived rather than directly acquired?", "kind": "definition", "id": "actual-lead-configuration-q01" }, { "text": "Were electrode locations standard for the declared configuration, modified or uncertain?", "kind": "provenance", "id": "actual-lead-configuration-q02" } ] } ] }, { "id": "time-and-signal-settings", "name": "Time and signal settings", "description": "Temporal coverage and transformations affecting waveform representation.", "findings": [ { "id": "recording-window-and-calibration", "name": "Recording window and calibration", "description": "Recording duration, simultaneity, calibration and processing needed to interpret the trace.", "questions": [ { "text": "What time window is represented, where are the gaps, and were displayed leads acquired simultaneously?", "kind": "measurement", "id": "recording-window-and-calibration-q01" }, { "text": "What sampling rate, gain, display speed and filters are known, and which settings are unavailable?", "kind": "provenance", "id": "recording-window-and-calibration-q02" } ] } ] } ] }, { "id": "waveform-integrity", "name": "Waveform integrity", "description": "Whether the electrical recording can support the intended observations and measurements.", "rationale": "Artefacts, placement errors and incomplete traces can imitate or obscure clinically relevant patterns.", "layers": [ { "id": "artefacts-and-placement-checks", "name": "Artefacts and placement checks", "description": "Technical disturbances and suspected acquisition errors in specific leads or intervals.", "findings": [ { "id": "localised-signal-limitations", "name": "Localised signal limitations", "description": "The extent and location of baseline drift, movement artefact, interference, clipping or possible lead misconnection.", "questions": [ { "text": "Which leads and time segments show artefact, dropout, clipping or unstable baseline?", "kind": "measurement", "id": "localised-signal-limitations-q01" }, { "text": "What evidence supports a suspected electrode-placement or lead-connection error, and has it been checked?", "kind": "provenance", "id": "localised-signal-limitations-q02" } ] } ] }, { "id": "fitness-for-interpretation", "name": "Fitness for interpretation", "description": "A question-specific judgement of which parts of the ECG remain usable.", "findings": [ { "id": "usable-evidence-and-repeat-need", "name": "Usable evidence and repeat need", "description": "Supported uses, unsupported conclusions and acquisition changes needed to resolve limitations.", "questions": [ { "text": "Which intended rhythm, interval or morphology assessments remain supported by the available signal?", "kind": "boundary", "id": "usable-evidence-and-repeat-need-q01" }, { "text": "What specific electrode check, setting correction or repeat acquisition would address the unresolved limitation?", "kind": "action", "id": "usable-evidence-and-repeat-need-q02" } ] } ] } ] }, { "id": "electrical-observations-and-interpretation", "name": "Electrical observations and interpretation", "description": "Measured features and interpretive statements grounded in identifiable waveform evidence.", "rationale": "The model must distinguish a waveform observation, a calculated quantity and a clinical interpretation.", "layers": [ { "id": "rhythm-and-waveform-measurements", "name": "Rhythm and waveform measurements", "description": "Rate, timing and morphology observations with their methods and evidence locations.", "findings": [ { "id": "trace-grounded-features", "name": "Trace-grounded features", "description": "Reported rhythm features, intervals, amplitudes and morphology tied to leads and representative beats.", "questions": [ { "text": "What rate, regularity, atrial-to-ventricular relationships and waveform features are observed, and in which leads and segments?", "kind": "measurement", "id": "trace-grounded-features-q01" }, { "text": "How were reported intervals and corrected values calculated, including beat selection and any QT correction formula?", "kind": "provenance", "id": "trace-grounded-features-q02" } ] } ] }, { "id": "interpretive-claims-and-limits", "name": "Interpretive claims and limits", "description": "Attributed interpretations, competing explanations and the limits of this recording.", "findings": [ { "id": "supported-interpretation", "name": "Supported interpretation", "description": "The meaning assigned to observations without equating an ECG pattern with a settled diagnosis.", "questions": [ { "text": "Which statements are direct observations, automated classifications or human interpretations, and who or what produced each?", "kind": "provenance", "id": "supported-interpretation-q01" }, { "text": "What alternative explanations and acquisition limitations constrain the interpretation?", "kind": "boundary", "id": "supported-interpretation-q02" }, { "text": "What cannot be excluded because the recording covers only these leads and this observation window?", "kind": "boundary", "id": "supported-interpretation-q03" } ] } ] } ] }, { "id": "comparison-review-and-disposition", "name": "Comparison, review and disposition", "description": "How this ECG is linked to prior evidence, reviewed and acted upon within an authorised workflow.", "rationale": "ECG meaning may depend on change over time, and a recorded result requires traceable review and communication.", "layers": [ { "id": "recording-lineage-and-comparison", "name": "Recording lineage and comparison", "description": "The connection between the procedure, its waveform versions and comparable earlier recordings.", "findings": [ { "id": "comparable-ecg-evidence", "name": "Comparable ECG evidence", "description": "Verified recording identity and the conditions under which serial differences can be assessed.", "questions": [ { "text": "What links this waveform and report version to the correct patient, acquisition time and recording device?", "kind": "provenance", "id": "comparable-ecg-evidence-q01" }, { "text": "Which prior ECG is being compared, and could lead placement, gain, filtering or acquisition context explain apparent changes?", "kind": "boundary", "id": "comparable-ecg-evidence-q02" } ] } ] }, { "id": "review-and-result-routing", "name": "Review and result routing", "description": "Interpretation authority, unresolved discrepancies and completion of result communication.", "findings": [ { "id": "reviewed-result-and-next-action", "name": "Reviewed result and next action", "description": "The current report status and traceable next steps under the applicable clinical process.", "questions": [ { "text": "Has an authorised reviewer assessed the trace, and how were disagreements with automated or earlier interpretations resolved?", "kind": "provenance", "id": "reviewed-result-and-next-action-q01" }, { "text": "Under the applicable workflow, does this result require routine reporting, prompt review or urgent escalation, and who determines that?", "kind": "action", "id": "reviewed-result-and-next-action-q02" }, { "text": "Who must receive the result, has receipt been acknowledged, and what review or acquisition task remains open?", "kind": "action", "id": "reviewed-result-and-next-action-q03" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "resting 12-lead ECG", "ambulatory/Holter ECG", "exercise/stress ECG", "continuous bedside/telemetry ECG", "event/loop recorder ECG", "high-resolution/signal-averaged ECG", "fetal ECG", "vectorcardiography" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of electrocardiography this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "scheme": "Wikidata", "value_or_pattern": "Q79785", "note": "electrocardiography" } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of electrocardiography this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "AHA/ACC/HRS recommendations for standardization and interpretation of the electrocardiogram (AHA/ACC/HRS)", "IEC 60601-2-25: Particular requirements for the basic safety and essential performance of electrocardiographs (IEC)", "IEC 60601-2-27: Particular requirements for electrocardiographic monitoring equipment (IEC)", "ISO 11073-91064 / SCP-ECG: Standard communications protocol for computer-assisted electrocardiography (ISO/CEN)", "FDA 21 CFR 870.2340: Electrocardiograph (FDA)" ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of electrocardiography this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "12-lead ECG in emergency departments and clinics to detect acute coronary syndrome, arrhythmia, and conduction block", "Continuous bedside or telemetry monitoring in ICU and ward settings", "Ambulatory Holter and event recorders for intermittent palpitations and syncope workup", "Exercise ECG for inducible ischemia and chronotropic assessment", "Pre-participation, preoperative, and occupational screening", "Device clinics and wearable consumer ECG (single-lead) with clinician overread" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of electrocardiography this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "quantity": "heart rate", "typical_range": "60-100 (resting adult)", "unit": "beats/min" }, { "quantity": "PR interval", "typical_range": "120-200", "unit": "ms" }, { "quantity": "QRS duration", "typical_range": "80-120", "unit": "ms" }, { "quantity": "QT interval (rate-corrected QTc)", "typical_range": "350-450 (sex-dependent)", "unit": "ms" }, { "quantity": "ST-segment deviation", "typical_range": "0 to ±1 (diagnostic thresholds higher by lead and sex)", "unit": "mm" }, { "quantity": "paper/display speed", "typical_range": "25 (standard); 50 also used", "unit": "mm/s" }, { "quantity": "amplitude calibration", "typical_range": "10", "unit": "mm/mV" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of electrocardiography this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Lead misplacement or limb-lead reversal producing false infarct or dextrocardia patterns", "Motion, tremor, and 50/60 Hz interference mimicking arrhythmia or ST change", "Filter and gain settings distorting ST segments or hiding pacing spikes", "Misdiagnosis of artifact as ventricular tachycardia leading to unnecessary shocks or drugs", "Electrical safety hazards (leakage current, defibrillator recovery) on connected equipment", "QTc-prolonging drugs and electrolyte disturbance causing torsades", "Over-reliance on automated interpretation without clinician review" ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of electrocardiography this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Cabrera (physically contiguous) vs standard limb-lead display order used in parts of Europe", "Right-sided (V3R-V6R) and posterior (V7-V9) leads more routinely added in some ACS protocols", "50 Hz vs 60 Hz notch filtering by mains frequency", "Mason-Likar torso limb electrodes common in stress/monitoring vs wrists/ankles at rest", "Pediatric and neonatal lead sets and voltage criteria differ from adult cutoffs" ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of electrocardiography this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "name": "echocardiography", "difference": "Ultrasound of cardiac structure and motion, not surface electrical potentials; no P-QRS-T waveform." }, { "name": "electrophysiology study (intracardiac ECG)", "difference": "Catheter electrodes inside the heart for mapping/ablation; not a surface 12-lead recording." }, { "name": "vectorcardiography", "difference": "Orthogonal XYZ loops of the same electrical field rather than scalar 12-lead traces." }, { "name": "photoplethysmography / pulse oximetry waveform", "difference": "Optical pulse volume, not myocardial voltage; cannot show P waves or QRS morphology." }, { "name": "magnetocardiography", "difference": "Magnetic field of cardiac currents, typically in a shielded room, not skin electrodes." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of electrocardiography this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already own electrocardiography or a materially equivalent concept, requiring this registry entry to link to it?", "Should this entry own complete ambulatory ECG sessions as well as individual acquisitions, or should monitoring programmes own session-level coverage and event aggregation?", "Which authoritative acquisition and interpretation standards should ground requirements for conventional, modified and wearable lead configurations?", "Which population-specific contexts require additional questions or interpretation constraints, including paediatric recordings and paced rhythms?", "Which local policies define review authority, escalation criteria and permitted agent actions for preliminary ECG results?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 30 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "abstract concept", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a electrocardiography, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise an electrocardiography procedure, assess whether its recording and interpretation are usable, and identify appropriate next actions within its authority.", "characteristics": { "substance": "activity", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: vectorcardiography, body surface potential mapping, veterinary electrocardiography, Fetal echocardiography, fetal electrocardiography.", "5 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 62 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "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 electrocardiography, and on what evidence are they told apart?" ], "whatItIsMadeOf": "something that happens over time", "physicalCharacter": [ "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." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Nothing to see. What is recognised is an instance of it, and which instances count is exactly what is argued about." ], "relatedModels": [ { "relation": "covers", "note": "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.", "targets": [ "vectorcardiography", "body surface potential mapping", "veterinary electrocardiography", "Fetal echocardiography", "fetal electrocardiography" ] } ], "standing": "Described in 62 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 5 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one electrocardiography from another, and a electrocardiography from things that resemble it.", "rationale": "Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.", "layers": [ { "id": "naming-and-identifiers", "name": "Names and identifiers", "description": "The names this thing goes by and the identifiers that survive translation and time.", "findings": [ { "id": "preferred-name-and-aliases", "name": "Preferred name, aliases and local names", "description": "Which name to use, which names mean the same thing, and which merely sound similar.", "questions": [ { "id": "preferred-name-and-aliases-q01", "text": "What identifies and describes the name of a electrocardiography, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "preferred-name-and-aliases-q02", "text": "Who or what asserted this about the name of a electrocardiography, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "preferred-name-and-aliases-q03", "text": "What may an agent decide or do once the name of a electrocardiography is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "stable-identifiers", "name": "Stable identifiers and external keys", "description": "Identifiers that keep pointing at this kind of thing across systems and languages.", "questions": [ { "id": "stable-identifiers-q01", "text": "What identifies and describes an identifier for a electrocardiography, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stable-identifiers-q02", "text": "Who or what asserted this about an identifier for a electrocardiography, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stable-identifiers-q03", "text": "What may an agent decide or do once an identifier for a electrocardiography is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "classification-and-granularity", "name": "Classification and granularity", "description": "Where a electrocardiography sits among kinds, and how finely a task needs to cut it.", "findings": [ { "id": "kind-and-parents", "name": "Kind, parents and neighbouring kinds", "description": "The classes this thing belongs to and the ones it is next to.", "questions": [ { "id": "kind-and-parents-q01", "text": "What identifies and describes the kind of a electrocardiography, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "kind-and-parents-q02", "text": "Who or what asserted this about the kind of a electrocardiography, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "kind-and-parents-q03", "text": "What may an agent decide or do once the kind of a electrocardiography is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "distinguishing-features", "name": "Distinguishing features", "description": "What separates a electrocardiography from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a electrocardiography, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "distinguishing-features-q02", "text": "Who or what asserted this about what distinguishes a electrocardiography, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "distinguishing-features-q03", "text": "What may an agent decide or do once what distinguishes a electrocardiography is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "state-and-lifecycle", "name": "State and lifecycle", "description": "The states a electrocardiography passes through and the events that move it between them.", "rationale": "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.", "layers": [ { "id": "lifecycle-stages", "name": "Lifecycle stages", "description": "From coming into existence to ceasing to be one of these.", "findings": [ { "id": "stages-and-transitions", "name": "Stages and transitions", "description": "The stages worth naming and what moves a electrocardiography between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a electrocardiography, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stages-and-transitions-q02", "text": "Who or what asserted this about the lifecycle of a electrocardiography, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stages-and-transitions-q03", "text": "What may an agent decide or do once the lifecycle of a electrocardiography is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "observations-and-status", "name": "Observations and current status", "description": "What is observed about a electrocardiography, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a electrocardiography is recorded so that it can be superseded rather than overwritten.", "questions": [ { "id": "observation-record-q01", "text": "What identifies and describes an observation of a electrocardiography, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "observation-record-q02", "text": "Who or what asserted this about an observation of a electrocardiography, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "observation-record-q03", "text": "What may an agent decide or do once an observation of a electrocardiography is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "process-and-outcome", "name": "Process, inputs and outcome", "description": "How a electrocardiography proceeds, what it needs and what it leaves behind.", "rationale": "An activity is known by its steps and its results, and both have to be recordable while it is still running.", "layers": [ { "id": "steps-and-sequence", "name": "Steps and sequence", "description": "The steps of a electrocardiography, their order and what may run in parallel.", "findings": [ { "id": "steps-and-preconditions", "name": "Steps, preconditions and completion", "description": "What has to be true before each step of a electrocardiography and what marks it done.", "questions": [ { "id": "steps-and-preconditions-q01", "text": "What identifies and describes a step of a electrocardiography, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "steps-and-preconditions-q02", "text": "Who or what asserted this about a step of a electrocardiography, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "steps-and-preconditions-q03", "text": "What may an agent decide or do once a step of a electrocardiography is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "inputs-and-results", "name": "Inputs, resources and results", "description": "What a electrocardiography consumes and what it produces.", "findings": [ { "id": "inputs-and-outputs", "name": "Inputs, outputs and side effects", "description": "The resources a electrocardiography takes and the results it leaves, wanted or not.", "questions": [ { "id": "inputs-and-outputs-q01", "text": "What identifies and describes the inputs and results of a electrocardiography, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "inputs-and-outputs-q02", "text": "Who or what asserted this about the inputs and results of a electrocardiography, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "inputs-and-outputs-q03", "text": "What may an agent decide or do once the inputs and results of a electrocardiography is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "definitions-in-contest", "name": "Definitions and who holds them", "description": "What electrocardiography is taken to mean, and by whom.", "rationale": "When a field disagrees about a concept, the disagreement is the content. A model that picks one definition silently destroys the information.", "layers": [ { "id": "competing-definitions", "name": "Competing definitions", "description": "The main readings and the traditions behind them.", "findings": [ { "id": "definition-map", "name": "Definitions and their holders", "description": "Each definition with the school or body that holds it.", "questions": [ { "id": "definition-map-q01", "text": "Which definitions of electrocardiography are in use, and which tradition or body holds each?", "kind": "definition" }, { "id": "definition-map-q02", "text": "What turns on the difference between them in practice?", "kind": "boundary" } ] } ] }, { "id": "operationalisation", "name": "Operationalisation", "description": "How it is measured or applied when it has to be.", "findings": [ { "id": "operational-record", "name": "Measures and proxies", "description": "Instruments and indicators used to stand in for it.", "questions": [ { "id": "operational-record-q01", "text": "How is electrocardiography operationalised or measured in practice, and by what instrument?", "kind": "measurement" }, { "id": "operational-record-q02", "text": "What does that operationalisation leave out, and when does that matter?", "kind": "boundary" } ] } ] } ] }, { "id": "instances-and-use", "name": "Instances, use and consequence", "description": "What counts as an instance of electrocardiography and what follows from calling something that.", "rationale": "Applying a concept is an act with consequences, so a model must say what the label licenses and what it does not.", "layers": [ { "id": "instances", "name": "What counts as an instance", "description": "Clear cases, borderline cases and non-cases.", "findings": [ { "id": "instance-tests", "name": "Tests for an instance", "description": "What would settle whether something falls under it.", "questions": [ { "id": "instance-tests-q01", "text": "What would settle whether something is an instance of electrocardiography?", "kind": "boundary" }, { "id": "instance-tests-q02", "text": "Which borderline cases are argued about, and on what grounds?", "kind": "definition" } ] } ] }, { "id": "consequence", "name": "Consequence of application", "description": "Rights, duties or decisions that follow from the label.", "findings": [ { "id": "consequence-record", "name": "What the label licenses", "description": "What an agent may do once something is classified this way.", "questions": [ { "id": "consequence-record-q01", "text": "What follows practically once something is treated as electrocardiography?", "kind": "action" }, { "id": "consequence-record-q02", "text": "What must an agent not infer from the label alone?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a electrocardiography came from and when it held.", "rationale": "A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.", "layers": [ { "id": "source-and-authority", "name": "Source and authority", "description": "Who said it, on what evidence, and how strongly.", "findings": [ { "id": "claim-provenance", "name": "Claim provenance and confidence", "description": "The authority behind each claim about a electrocardiography and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a electrocardiography, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "claim-provenance-q02", "text": "Who or what asserted this about a claim about a electrocardiography, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "claim-provenance-q03", "text": "What may an agent decide or do once a claim about a electrocardiography is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "time-and-versions", "name": "Time, versions and supersession", "description": "When a claim was true, when it was learnt, and what replaced it.", "findings": [ { "id": "validity-and-supersession", "name": "Validity period and supersession", "description": "How an old claim about a electrocardiography is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a electrocardiography, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "validity-and-supersession-q02", "text": "Who or what asserted this about the validity of a claim about a electrocardiography, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "validity-and-supersession-q03", "text": "What may an agent decide or do once the validity of a claim about a electrocardiography is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 12, "findings": 14, "questions": 38 } } } }