@prefix : <#> .
@prefix schema: <http://schema.org/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix os: <https://linkeddata.uriburner.com/DAV/demos/daas/hospital-os-rdf-harness/ontology.ttl#> .

<> a schema:CreativeWork ;
    schema:name "Hospital Operating System — Sepsis Protocol Worked Example"@en ;
    schema:description "ABox instantiating one Clinical Pathway (adult, ED-initiated sepsis protocol) end to end across all ten operating-model categories, per os:hospitalOS. A single worked example, not a full task inventory: sample terminology codes and volumes are illustrative, not verified against a live terminology server or real hospital data."@en ;
    schema:dateCreated "2026-08-04"^^xsd:date ;
    schema:about :sepsisPathway ;
    rdfs:seeAlso <ontology.ttl> .

# ── Terminology & Ontologies ────────────────────────────────────────────────

:tcSepsis a os:TerminologyConcept ;
    skos:prefLabel "Sepsis (disorder)"@en ;
    skos:notation "91302008 (illustrative SNOMED CT-style code)"@en ;
    rdfs:comment "Illustrative terminology binding — not verified against a live SNOMED CT terminology server."@en .

:tcSepticShock a os:TerminologyConcept ;
    skos:prefLabel "Septic shock (disorder)"@en ;
    skos:broader :tcSepsis ;
    rdfs:comment "Illustrative terminology binding."@en .

:tcLactateTest a os:TerminologyConcept ;
    skos:prefLabel "Lactate measurement, serum"@en ;
    rdfs:comment "Illustrative LOINC-style order-catalog term."@en .

:tcPiperacillinTazobactam a os:TerminologyConcept ;
    skos:prefLabel "Piperacillin+Tazobactam"@en ;
    rdfs:comment "Illustrative formulary/RxNorm-style term."@en .

# ── Master Data ──────────────────────────────────────────────────────────────

:mdPatientRecord a os:MasterDataEntity ;
    schema:name "Patient / EHR Record"@en ;
    rdfs:comment "Governed reference record read and updated throughout the pathway."@en .

:mdAntibioticFormularyItem a os:MasterDataEntity ;
    schema:name "Antibiotic Formulary Item — Piperacillin-Tazobactam"@en ;
    os:usesTerminology :tcPiperacillinTazobactam .

:mdLabOrderCatalogItem a os:MasterDataEntity ;
    schema:name "Lab Order Catalog Item — Serum Lactate"@en ;
    os:usesTerminology :tcLactateTest .

# ── Logistics & Resources ───────────────────────────────────────────────────

:resEdBed a os:LogisticsResource ;
    schema:name "ED Monitored Bed"@en .

:resIvPump a os:LogisticsResource ;
    schema:name "IV Infusion Pump"@en .

:resAntibioticStock a os:LogisticsResource ;
    schema:name "Pharmacy Antibiotic Stock — Piperacillin-Tazobactam"@en .

# ── Policies & Governance ───────────────────────────────────────────────────

:policySepsisScreening a os:Policy ;
    schema:name "Sepsis Screening Policy"@en ;
    schema:description "Mandates qSOFA/SIRS screening for any ED patient with suspected infection, at first triage contact."@en .

:policyAntibioticStewardship a os:Policy ;
    schema:name "Antibiotic Stewardship Policy"@en ;
    schema:description "Requires pharmacist review of broad-spectrum antibiotic orders against allergy and resistance data before dispensing, except in documented Code Sepsis time-critical overrides."@en .

:policyEscalation a os:Policy ;
    schema:name "Critical Care Escalation Policy"@en ;
    schema:description "Defines the vital-sign and lactate-clearance thresholds that require ICU consultation."@en .

# ── Decision Rights ──────────────────────────────────────────────────────────

:drInitiateSepsisBundle a os:DecisionRight ;
    schema:name "Right to Initiate Sepsis Bundle"@en ;
    os:heldBy :roleEdPhysician .

:drOverrideStewardshipHold a os:DecisionRight ;
    schema:name "Right to Override Stewardship Hold (Code Sepsis)"@en ;
    os:heldBy :roleEdPhysician .

:drEscalateToIcu a os:DecisionRight ;
    schema:name "Right to Escalate to ICU"@en ;
    os:heldBy :roleChargeNurse .

# ── Tasks & Workforce (roles) ────────────────────────────────────────────────

:roleTriageNurse a os:WorkforceRole ;
    schema:name "Triage Nurse"@en .

:roleEdPhysician a os:WorkforceRole ;
    schema:name "ED Attending Physician"@en .

:rolePharmacist a os:WorkforceRole ;
    schema:name "Clinical Pharmacist"@en .

:roleLabTech a os:WorkforceRole ;
    schema:name "Lab Technician"@en .

:roleChargeNurse a os:WorkforceRole ;
    schema:name "ED Charge Nurse"@en .

# ── Performance & Quality ───────────────────────────────────────────────────

:metricTimeToAntibiotics a os:PerformanceMetric ;
    schema:name "Time to First Antibiotic Dose"@en ;
    os:metricTargetValue 60.0 ;
    os:metricUnit "minutes"@en .

:metricLactateClearance a os:PerformanceMetric ;
    schema:name "6-Hour Lactate Clearance Rate"@en ;
    os:metricTargetValue 10.0 ;
    os:metricUnit "percent"@en .

:metricBundleCompliance a os:PerformanceMetric ;
    schema:name "Sepsis Bundle Compliance Rate"@en ;
    os:metricTargetValue 90.0 ;
    os:metricUnit "percent"@en .

:metric30DayMortality a os:PerformanceMetric ;
    schema:name "30-Day Sepsis Mortality Rate"@en ;
    os:metricUnit "percent"@en .

# ── Clinical Pathway ─────────────────────────────────────────────────────────

:sepsisPathway a os:ClinicalPathway ;
    schema:name "Sepsis Protocol (Adult, ED-Initiated)"@en ;
    schema:description "Ordered protocol from ED triage through initial bundle completion and escalation decision."@en ;
    os:usesTerminology :tcSepsis, :tcSepticShock ;
    os:estimatedAnnualTaskVolume 8400 ;
    os:hasStep :stepTriage, :stepDiagnostics, :stepAntibiotics, :stepFluidResuscitation, :stepReassessment ;
    os:governedByPolicy :policySepsisScreening ;
    os:measuredBy :metricTimeToAntibiotics, :metricLactateClearance, :metricBundleCompliance, :metric30DayMortality .

# ── Workflow Steps (ordered) ─────────────────────────────────────────────────

:stepTriage a os:WorkflowStep ;
    schema:name "Triage & Recognition"@en ;
    os:stepOrder 1 ;
    os:nextStep :stepDiagnostics ;
    os:hasTask :taskScreenQsofa .

:stepDiagnostics a os:WorkflowStep ;
    schema:name "Diagnostics: Lactate & Cultures"@en ;
    os:stepOrder 2 ;
    os:nextStep :stepAntibiotics ;
    os:hasTask :taskDrawLactate, :taskDrawBloodCultures .

:stepAntibiotics a os:WorkflowStep ;
    schema:name "Broad-Spectrum Antibiotic Administration"@en ;
    os:stepOrder 3 ;
    os:nextStep :stepFluidResuscitation ;
    os:hasTask :taskReviewAntibioticOrder, :taskAdministerAntibiotic .

:stepFluidResuscitation a os:WorkflowStep ;
    schema:name "IV Fluid Resuscitation"@en ;
    os:stepOrder 4 ;
    os:nextStep :stepReassessment ;
    os:hasTask :taskAdministerFluidBolus .

:stepReassessment a os:WorkflowStep ;
    schema:name "Reassessment & Escalation Decision"@en ;
    os:stepOrder 5 ;
    os:hasTask :taskReassessLactate, :taskEscalationDecision .

# ── Tasks ─────────────────────────────────────────────────────────────────────

:taskScreenQsofa a os:Task ;
    schema:name "Perform qSOFA/SIRS Screening"@en ;
    os:performedBy :roleTriageNurse ;
    os:referencesMasterData :mdPatientRecord ;
    os:governedByPolicy :policySepsisScreening ;
    os:usesTerminology :tcSepsis .

:taskDrawLactate a os:Task ;
    schema:name "Order & Draw Serum Lactate"@en ;
    os:performedBy :roleLabTech ;
    os:referencesMasterData :mdLabOrderCatalogItem ;
    os:usesTerminology :tcLactateTest .

:taskDrawBloodCultures a os:Task ;
    schema:name "Draw Blood Cultures (Pre-Antibiotic)"@en ;
    os:performedBy :roleLabTech ;
    os:referencesMasterData :mdPatientRecord .

:taskReviewAntibioticOrder a os:Task ;
    schema:name "Review Antibiotic Order for Stewardship"@en ;
    os:performedBy :rolePharmacist ;
    os:referencesMasterData :mdAntibioticFormularyItem ;
    os:governedByPolicy :policyAntibioticStewardship ;
    os:hasDecisionRight :drOverrideStewardshipHold .

:taskAdministerAntibiotic a os:Task ;
    schema:name "Administer First Antibiotic Dose"@en ;
    os:performedBy :roleEdPhysician ;
    os:consumesResource :resAntibioticStock, :resIvPump ;
    os:referencesMasterData :mdAntibioticFormularyItem ;
    os:hasDecisionRight :drInitiateSepsisBundle ;
    os:measuredBy :metricTimeToAntibiotics .

:taskAdministerFluidBolus a os:Task ;
    schema:name "Administer 30 mL/kg IV Fluid Bolus"@en ;
    os:performedBy :roleTriageNurse ;
    os:consumesResource :resIvPump, :resEdBed .

:taskReassessLactate a os:Task ;
    schema:name "Repeat Lactate & Vital Sign Reassessment"@en ;
    os:performedBy :roleLabTech ;
    os:referencesMasterData :mdLabOrderCatalogItem ;
    os:measuredBy :metricLactateClearance .

:taskEscalationDecision a os:Task ;
    schema:name "Determine ICU Escalation"@en ;
    os:performedBy :roleChargeNurse ;
    os:governedByPolicy :policyEscalation ;
    os:hasDecisionRight :drEscalateToIcu ;
    os:usesTerminology :tcSepticShock ;
    os:measuredBy :metric30DayMortality .

# ── WebPage (this infographic) ──────────────────────────────────────────────

:hospitalOSPage a schema:WebPage ;
    schema:name "Hospital Operating System — Sepsis Protocol Worked Example"@en ;
    schema:about :sepsisPathway ;
    schema:hasPart :hospitalOSFaq, :hospitalOSGlossary, :sepsisPathwayHowTo ;
    schema:isBasedOn :originatingPost, :followUpPost .

# ── FAQ (schema:Question / schema:Answer) ───────────────────────────────────

:hospitalOSFaq a schema:ItemList ;
    schema:name "Hospital Operating System — Frequently Asked Questions"@en ;
    schema:itemListElement :faqQ1, :faqQ2, :faqQ3, :faqQ4, :faqQ5,
        :faqQ6, :faqQ7, :faqQ8, :faqQ9, :faqQ10 .

:faqQ1 a schema:Question ;
    schema:name "What does the 'Operating System' box represent, versus the 'Structural Design' box?"@en ;
    schema:acceptedAnswer :faqA1 .
:faqA1 a schema:Answer ;
    schema:text "The Operating System box models how the hospital works — clinical pathways, workflows, tasks, workforce roles, master data, policies, decision rights, logistics, and performance metrics. The Structural Design box models where the hospital works — the physical building, floor plans, and infrastructure. This ontology and its worked example model only the former."@en .

:faqQ2 a schema:Question ;
    schema:name "Why is Knowledge Graph modeled as a superclass rather than a tenth sibling category?"@en ;
    schema:acceptedAnswer :faqA2 .
:faqA2 a schema:Answer ;
    schema:text "In the source framing, the Knowledge Graph is the connective layer that indexes and links the other nine categories, not an isolated concept type sitting beside them. os:KnowledgeGraphComponent is therefore a marker rdfs:Class that every other category rdfs:subClassOf's, so any instance of any category is automatically a graph node."@en .

:faqQ3 a schema:Question ;
    schema:name "What does the sepsis pathway's 'what, by whom, with what, in what sequence, under what rules' framing map to in the ontology?"@en ;
    schema:acceptedAnswer :faqA3 .
:faqA3 a schema:Answer ;
    schema:text "os:hasTask/os:Task answers what is done; os:performedBy answers by whom; os:referencesMasterData and os:consumesResource answer with what; os:stepOrder and os:nextStep answer in what sequence; and os:governedByPolicy plus os:hasDecisionRight answer under what rules."@en .

:faqQ4 a schema:Question ;
    schema:name "How many Task instances does the source framing say the real operating model spans?"@en ;
    schema:acceptedAnswer :faqA4 .
:faqA4 a schema:Answer ;
    schema:text "The source infographic states the Operating System layer spans roughly 30,000 to 60,000 tasks hospital-wide, across thousands of concepts. This worked example instantiates one pathway (9 tasks, os:estimatedAnnualTaskVolume 8400 firings/year) as a representative sample, not the full inventory."@en .

:faqQ5 a schema:Question ;
    schema:name "What is a Clinical Pathway in this model?"@en ;
    schema:acceptedAnswer :faqA5 .
:faqA5 a schema:Answer ;
    schema:text "An os:ClinicalPathway is an ordered, protocol-driven sequence of care for a condition, composed of os:WorkflowStep instances via os:hasStep. This example's :sepsisPathway has five ordered steps from triage through escalation decision."@en .

:faqQ6 a schema:Question ;
    schema:name "How are Terminology Concepts related to skos:Concept?"@en ;
    schema:acceptedAnswer :faqA6 .
:faqA6 a schema:Answer ;
    schema:text "os:TerminologyConcept is declared rdfs:subClassOf skos:Concept, so every terminology instance can use skos:prefLabel, skos:notation, and skos:broader/skos:narrower directly rather than a bespoke vocabulary. The example's terminology codes are marked illustrative and not verified against a live terminology server."@en .

:faqQ7 a schema:Question ;
    schema:name "How does a Decision Right differ from a Policy?"@en ;
    schema:acceptedAnswer :faqA7 .
:faqA7 a schema:Answer ;
    schema:text "An os:Policy is a governance rule that constrains how work is carried out; an os:DecisionRight is a specific authority to make a decision, held by exactly one os:WorkforceRole via os:heldBy. A single task can be governed by a Policy and simultaneously require exercising a Decision Right — for example, antibiotic review is governed by the stewardship Policy while the physician separately holds the right to override its hold in a documented emergency."@en .

:faqQ8 a schema:Question ;
    schema:name "What connects a Task to the Performance & Quality category?"@en ;
    schema:acceptedAnswer :faqA8 .
:faqA8 a schema:Answer ;
    schema:text "os:measuredBy links an os:Task or os:ClinicalPathway to an os:PerformanceMetric, which carries os:metricTargetValue and os:metricUnit. The pathway-level metrics (time-to-antibiotics, lactate clearance, bundle compliance, 30-day mortality) roll up task-level measurement points into pathway-level quality evaluation."@en .

:faqQ9 a schema:Question ;
    schema:name "Is this ontology intended to be a complete hospital data model?"@en ;
    schema:acceptedAnswer :faqA9 .
:faqA9 a schema:Answer ;
    schema:text "No. It is a mockup harness derived from the agent-rdf-memory authoring conventions, scoped to demonstrate the ten-category structure and its relations with one fully worked pathway. It is meant as a starting point for building out further pathways, not a validated clinical or operational system."@en .

:faqQ10 a schema:Question ;
    schema:name "How would a new pathway be added to this model?"@en ;
    schema:acceptedAnswer :faqA10 .
:faqA10 a schema:Answer ;
    schema:text "Follow the ten-step checklist in howto/instantiate-new-pathway.ttl: mint the pathway entity, bind terminology, lay out ordered workflow steps, attach tasks, assign performing roles, attach master data/resources, attach governing policy, attach decision rights, attach performance metrics, and set an illustrative annual task volume."@en .

# ── Glossary (schema:DefinedTermSet / schema:DefinedTerm) ──────────────────

:hospitalOSGlossary a schema:DefinedTermSet ;
    schema:name "Hospital Operating System Glossary"@en ;
    schema:hasDefinedTerm :glClinicalPathway, :glTerminologyConcept, :glWorkflowStep,
        :glKnowledgeGraphComponent, :glTask, :glWorkforceRole, :glMasterDataEntity,
        :glPolicy, :glDecisionRight, :glLogisticsResource, :glPerformanceMetric .

:glClinicalPathway a schema:DefinedTerm ;
    schema:name "Clinical Pathway"@en ;
    schema:description "An ordered, protocol-driven sequence of care for a clinical condition, composed of ordered workflow steps."@en ;
    schema:inDefinedTermSet :hospitalOSGlossary .

:glTerminologyConcept a schema:DefinedTerm ;
    schema:name "Terminology Concept"@en ;
    schema:description "A standardized clinical or operational term used to bind pathways, tasks, and master data to a controlled vocabulary, modeled as a skos:Concept."@en ;
    schema:inDefinedTermSet :hospitalOSGlossary .

:glWorkflowStep a schema:DefinedTerm ;
    schema:name "Workflow Step"@en ;
    schema:description "One ordered stage of a clinical pathway, grouping the tasks performed at that stage."@en ;
    schema:inDefinedTermSet :hospitalOSGlossary .

:glKnowledgeGraphComponent a schema:DefinedTerm ;
    schema:name "Knowledge Graph Component"@en ;
    schema:description "The marker superclass for any entity that participates as a node in the hospital operating-model knowledge graph — the connective layer spanning the other nine categories."@en ;
    schema:inDefinedTermSet :hospitalOSGlossary .

:glTask a schema:DefinedTerm ;
    schema:name "Task"@en ;
    schema:description "A discrete unit of work within a workflow step; the operating model is described as spanning roughly 30,000-60,000 such tasks hospital-wide."@en ;
    schema:inDefinedTermSet :hospitalOSGlossary .

:glWorkforceRole a schema:DefinedTerm ;
    schema:name "Workforce Role"@en ;
    schema:description "A staff role, by job function rather than named individual, that performs tasks."@en ;
    schema:inDefinedTermSet :hospitalOSGlossary .

:glMasterDataEntity a schema:DefinedTerm ;
    schema:name "Master Data Entity"@en ;
    schema:description "A governed reference-data record — a patient record, formulary item, or order-catalog entry — that a task reads or writes."@en ;
    schema:inDefinedTermSet :hospitalOSGlossary .

:glPolicy a schema:DefinedTerm ;
    schema:name "Policy"@en ;
    schema:description "A governance rule that constrains how a task, workflow step, or pathway may be carried out."@en ;
    schema:inDefinedTermSet :hospitalOSGlossary .

:glDecisionRight a schema:DefinedTerm ;
    schema:name "Decision Right"@en ;
    schema:description "An authority to make a specific class of decision, held by a workforce role and scoped to a task or pathway."@en ;
    schema:inDefinedTermSet :hospitalOSGlossary .

:glLogisticsResource a schema:DefinedTerm ;
    schema:name "Logistics Resource"@en ;
    schema:description "A physical or schedulable resource — a bed, piece of equipment, or stock item — consumed or occupied by a task."@en ;
    schema:inDefinedTermSet :hospitalOSGlossary .

:glPerformanceMetric a schema:DefinedTerm ;
    schema:name "Performance Metric"@en ;
    schema:description "A quality or performance measure, with a target value and unit, used to evaluate a pathway or task."@en ;
    schema:inDefinedTermSet :hospitalOSGlossary .

# ── HowTo (reuses the pathway's own WorkflowStep chain as its steps) ───────

:sepsisPathwayHowTo a schema:HowTo ;
    schema:name "How the Sepsis Protocol Pathway Executes"@en ;
    schema:description "The pathway's own five ordered workflow steps, presented as a HowTo: each step is simultaneously an os:WorkflowStep in the operating-model graph and a schema:HowToStep in this narrative."@en ;
    schema:step :stepTriage, :stepDiagnostics, :stepAntibiotics, :stepFluidResuscitation, :stepReassessment .

:stepTriage a schema:HowToStep ;
    schema:position 1 ;
    schema:name "Triage & Recognition"@en ;
    schema:text "Triage nurse performs qSOFA/SIRS screening against the patient record, governed by the sepsis screening policy."@en .

:stepDiagnostics a schema:HowToStep ;
    schema:position 2 ;
    schema:name "Diagnostics: Lactate & Cultures"@en ;
    schema:text "Lab technician orders and draws serum lactate and pre-antibiotic blood cultures."@en .

:stepAntibiotics a schema:HowToStep ;
    schema:position 3 ;
    schema:name "Broad-Spectrum Antibiotic Administration"@en ;
    schema:text "Pharmacist reviews the antibiotic order for stewardship (with override right in a Code Sepsis emergency); ED physician administers the first dose, measured against the time-to-antibiotics metric."@en .

:stepFluidResuscitation a schema:HowToStep ;
    schema:position 4 ;
    schema:name "IV Fluid Resuscitation"@en ;
    schema:text "Triage nurse administers a 30 mL/kg IV fluid bolus, consuming the infusion pump and ED bed."@en .

:stepReassessment a schema:HowToStep ;
    schema:position 5 ;
    schema:name "Reassessment & Escalation Decision"@en ;
    schema:text "Lab technician repeats lactate and vital-sign reassessment; charge nurse exercises the ICU-escalation decision right under the critical care escalation policy."@en .

# ── People (Source & Discussion) ────────────────────────────────────────────
# Canonical platform IRIs used directly as sole subjects — no document-local
# IRI, per agent-rdf-memory/howto/canonical-entity-iri-denotation.ttl Step 7
# (:step-localIriProhibition). www.linkedin.com is canonical (user-supplied);
# ae.linkedin.com (regional subdomain, observed live on the rendered post) is
# linked via owl:sameAs, not created as a separate local alias.

<https://www.linkedin.com/in/brian-de-francesca#this> a schema:Person ;
    schema:name "Brian de Francesca"@en ;
    schema:description "Author of the LinkedIn thesis 'Most hospitals were never fully designed' and its forthcoming paper 'The Hospital That Was Never Fully Designed,' arguing hospital operating architecture (pathways, workflows, decision rights, terminology) must be designed before the physical building. This document's ten-category ontology is an independently modeled harness inspired by his framing, not authored, reviewed, or endorsed by him."@en ;
    owl:sameAs <https://ae.linkedin.com/in/brian-de-francesca#this> .

<https://www.linkedin.com/in/kidehen#this> a schema:Person ;
    schema:name "Kingsley Uyi Idehen"@en ;
    schema:description "Principal on whose behalf this Knowledge Graph and infographic were curated. Commented on Brian de Francesca's follow-up LinkedIn post asking how the operating-architecture 'map' can be built without introducing compounding technical debt — the question this hospital-os-rdf-harness worked example attempts one answer to."@en .

# ── Source Posts & Comment (local IRIs — no canonical platform entity IRI
# ladder exists for individual social posts/comments themselves; schema:url
# carries the actual dereferenceable link. schema:author still points to the
# canonical Person IRIs above directly, per canonical-entity-iri-denotation.ttl.)

:originatingPost a schema:SocialMediaPosting ;
    schema:name "Most hospitals were never fully designed"@en ;
    schema:author <https://www.linkedin.com/in/brian-de-francesca#this> ;
    schema:url <https://www.linkedin.com/posts/brian-de-francesca_most-hospitals-were-never-fully-designed-activity-7486290293886005248-2CRg> ;
    schema:abstract "Hospital buildings, equipment, and staff get designed and procured individually, but the operating architecture that determines how they function together — pathways, workflows, decision rights, task allocations, terminology — is rarely designed as one system before the doors open. Cites a study finding workarounds in 62.7% of 5,793 observed medication administrations as evidence the designed process does not describe the actual work."@en ;
    schema:about :sepsisPathway .

:followUpPost a schema:SocialMediaPosting ;
    schema:name "Physical structures are derivative of operating systems, which are derivative of intelligence"@en ;
    schema:author <https://www.linkedin.com/in/brian-de-francesca#this> ;
    schema:url <https://www.linkedin.com/feed/update/urn:li:activity:7489378571585634305> ;
    schema:abstract "Argues that a hospital's physical structure is the built consequence of where and how intelligence (monitoring, interpretation) had to be located at the time of design — e.g. the Nightingale ward as a consequence of embodied, line-of-sight nurse monitoring. Once built, structure constrains the operating system for decades, which in turn constrains how new intelligence can be deployed: 'the derivative becomes the determinant.'"@en ;
    schema:comment :kingsleyComment .

:kingsleyComment a schema:Comment ;
    schema:author <https://www.linkedin.com/in/kidehen#this> ;
    schema:text "Yes, this is reality. The question is: how is the problem solved? Fundamentally, how is the map built without introducing compounding technical debt?"@en ;
    schema:isPartOf :followUpPost ;
    schema:about :sepsisPathway .