Property Graph Model

Unlike relational databases where connections are implied through foreign keys and joins, the property graph model treats relationships as first-class citizens. Each edge has a unique type, a direction, and its own set of properties. This allows for materializing complex paths directly in the data model, enabling constant-time traversal of connections like (Patient)-[:HAS_CONDITION]->(Diagnosis) without expensive table scans.

Nodes and relationships are grouped using labels (e.g., :Patient, :Drug, :TREATS), which define roles without enforcing a rigid schema. A single node can have multiple labels, allowing for polymorphic queries. This is critical in healthcare, where a single entity might be both a :Patient and a :ResearchSubject. Properties are stored as key-value pairs, allowing sparse attributes without NULL overhead.

The physical storage layer of native graph databases implements index-free adjacency, where each node maintains direct physical pointers to its neighboring nodes. This ensures that traversal speed is not dependent on the total size of the dataset, but only on the number of relationships traversed. For clinical graph queries like finding all co-morbidities of a specific patient, performance remains constant regardless of database scale.

Both nodes and relationships act as containers for arbitrary key-value properties. A :Medication node can store {name: 'Metformin', dosage: '500mg', frequency: 'BID'}, while the [:PRESCRIBED_BY] relationship can store {date: '2024-01-15', refills: 3}. This eliminates the need for complex join tables to capture contextual metadata about the connection itself.

Query languages like Cypher (openCypher) use ASCII-art syntax to declaratively express graph patterns. A query like (p:Patient {id: '123'})-[:HAS_LAB]->(l:LabResult)-[:INDICATES]->(c:Condition) visually matches the graph structure. This pattern-matching approach is highly intuitive for expressing complex clinical pathways and temporal relationships without recursive SQL.

The model aligns directly with conceptual diagrams drawn by domain experts. A clinician's whiteboard sketch of a care pathway—showing entities like Patient, Visit, and Procedure connected by arrows—maps directly to the logical model without the object-relational impedance mismatch required to flatten the structure into normalized tables. This accelerates agile development in clinical informatics.