Release 4B

This page is part of the FHIR Specification (v4.3.0: R4B - STU). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Riskassessment-example-population.ttl

Clinical Decision Support Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Device, Patient, Practitioner

Raw Turtle (+ also see Turtle/RDF Format Specification)

Public health population risk assessment

@prefix fhir: <http://hl7.org/fhir/> .
@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#> .

# - resource -------------------------------------------------------------------

<http://hl7.org/fhir/RiskAssessment/population> a fhir:RiskAssessment;
  fhir:nodeRole fhir:treeRoot;
  fhir:Resource.id [ fhir:value "population"];
  fhir:DomainResource.text [
     fhir:Narrative.status [ fhir:value "generated" ];
     fhir:Narrative.div "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n      <p>Todo - e.g. probable number of infections in a given region over a time period for a given disease based on vaccination rates and other factors</p>\n    </div>"
  ];
  fhir:DomainResource.contained [
     a fhir:Group;
     fhir:index 0;
     fhir:Resource.id [ fhir:value "group1" ];
     fhir:Group.type [ fhir:value "person" ];
     fhir:Group.actual [ fhir:value "false"^^xsd:boolean ]
  ];
  fhir:RiskAssessment.status [ fhir:value "final"];
  fhir:RiskAssessment.subject [
     fhir:Reference.reference [ fhir:value "#group1" ]
  ] .

# - ontology header ------------------------------------------------------------

<http://hl7.org/fhir/RiskAssessment/population.ttl> a owl:Ontology;
  owl:imports fhir:fhir.ttl;
  owl:versionIRI <http://build.fhir.org/RiskAssessment/population.ttl> .

# -------------------------------------------------------------------------------------


Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.