@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 os: <../ontology.ttl#> .

<> a schema:CreativeWork ;
    schema:name "How To Instantiate a New Clinical Pathway"@en ;
    schema:description "Reusable pattern for adding another os:ClinicalPathway to entities.ttl (or a sibling file) following the Sepsis Protocol worked example, so the mockup can grow to cover additional pathways without re-deriving the ontology."@en ;
    schema:dateCreated "2026-08-04"^^xsd:date ;
    schema:about :instantiateNewPathway ;
    rdfs:seeAlso <../ontology.ttl>, <../entities.ttl> .

:instantiateNewPathway a schema:HowTo ;
    schema:name "Instantiate a New Clinical Pathway"@en ;
    schema:description "Ten-step checklist for adding a new os:ClinicalPathway instance that stays consistent with os:hospitalOS."@en ;
    schema:step :step1, :step2, :step3, :step4, :step5, :step6, :step7, :step8, :step9, :step10 .

:step1 a schema:HowToStep ;
    schema:position 1 ;
    schema:name "Mint the pathway entity"@en ;
    schema:text "Create one os:ClinicalPathway instance with schema:name and schema:description. Use a local # fragment IRI, not a blank node."@en .

:step2 a schema:HowToStep ;
    schema:position 2 ;
    schema:name "Bind terminology first"@en ;
    schema:text "Before writing steps or tasks, mint or reuse the os:TerminologyConcept instances the pathway depends on (condition, key labs, key drugs), each with skos:prefLabel. Mark illustrative codes with rdfs:comment noting they are not verified against a live terminology server, as done for :tcSepsis."@en .

:step3 a schema:HowToStep ;
    schema:position 3 ;
    schema:name "Lay out ordered workflow steps"@en ;
    schema:text "Create one os:WorkflowStep per pathway stage, each with os:stepOrder (1-based integer) and os:nextStep chaining to the following step. The final step omits os:nextStep."@en .

:step4 a schema:HowToStep ;
    schema:position 4 ;
    schema:name "Attach tasks to each step"@en ;
    schema:text "For each os:WorkflowStep, create the os:Task instances it contains and link them with os:hasTask. A step may have one or several tasks."@en .

:step5 a schema:HowToStep ;
    schema:position 5 ;
    schema:name "Assign the performing role"@en ;
    schema:text "Every os:Task must have exactly one os:performedBy pointing to an os:WorkforceRole. Reuse an existing role instance where the job function matches; only mint a new role when the pathway introduces a genuinely new function."@en .

:step6 a schema:HowToStep ;
    schema:position 6 ;
    schema:name "Attach master data and resources"@en ;
    schema:text "Use os:referencesMasterData for governed reference records the task reads/writes (charts, orders, formulary items) and os:consumesResource for physical or schedulable resources (beds, pumps, stock). A task may use neither, either, or both."@en .

:step7 a schema:HowToStep ;
    schema:position 7 ;
    schema:name "Attach governing policy"@en ;
    schema:text "Where a rule constrains how the task, step, or pathway may be carried out, link it with os:governedByPolicy to an existing or new os:Policy instance."@en .

:step8 a schema:HowToStep ;
    schema:position 8 ;
    schema:name "Attach decision rights"@en ;
    schema:text "Where a task requires an authorized decision, create or reuse an os:DecisionRight, link it to the task with os:hasDecisionRight, and set its os:heldBy to the os:WorkforceRole authorized to exercise it."@en .

:step9 a schema:HowToStep ;
    schema:position 9 ;
    schema:name "Attach performance metrics"@en ;
    schema:text "Create os:PerformanceMetric instances for what the pathway is evaluated against, set os:metricTargetValue and os:metricUnit where a numeric target applies, and link them to the pathway (and to individual tasks where a metric is task-specific) with os:measuredBy."@en .

:step10 a schema:HowToStep ;
    schema:position 10 ;
    schema:name "Set the illustrative volume"@en ;
    schema:text "Set os:estimatedAnnualTaskVolume on the pathway to a plausible order-of-magnitude figure, and note in schema:description that it is illustrative — this is what ties the worked example back to the source framing's hospital-wide 30,000-60,000 task figure without claiming it as verified operational data."@en .