4 · The Ontology — annotated Turtle

Architecture of medacore.ttl

The Turtle file displayed below represents the entirety of the logic required by the reasoner. Let's break it down architecturally:

1. The Core Metadata Header: Notice the ontology IRI, combined with the owl:versionIRI and copyright license. By mapping this to a w3id.org Persistent URL (PURL), we create an immutable, globally resolvable web identifier that we completely control, without worrying about specific DNS registrar lock-ins.
2. The Foundational Classes: We define the six primary entities. Crucially, four are wrapped in an owl:AllDisjointClasses axiom. This provides powerful safety: it's mathematically impossible for an entity to be simultaneously registered as an AdverseEvent and a DrugExposure. Any bad data attempting this will trigger an immediate logical contradiction alert.
3. Semantic Properties: Object and datatype properties establish the edges of our graph, secured by explicit rdfs:domain and rdfs:range designations. (Remember: In OWL, domain/range act as inference engines to classify unknown nodes, NOT as validations to block bad data. We rely on SHACL for validation.)
4. The Defined Classes (The Magic): This is where the magic happens. We build logically compound classes like :SeriousAdverseEvent and :ReportableCase. The reasoner will dynamically classify instances into these groups. This is the literal embodiment of MedaCore's regulatory business rule.

Hands-On Experiment

Go into the playground editor below. In the data file, change the severity from "severe" to "moderate". Re-run the reasoning engine. You will dynamically observe that the event is gracefully demoted from the SeriousAdverseEvent classification, and consequently falls out of the ReportableCase bucket entirely. That transparent, unbroken traceability is your auditable inference chain.