Clinical Document Shape
Validation constraints for clinical documents imported from EHR
Imported At
Clinical document must have exactly one importedAt timestamp
Source EHR
Clinical document must specify the source EHR system
Source Bundle ID
Bundle ID must be a valid iOS bundle identifier
FHIR Resource ID
Clinical document must have a FHIR resource ID
FHIR Resource Type
Clinical document must specify FHIR resource type
Display Name
Narrative Text
Plain text content extracted from FHIR narrative
Narrative XHTML
Raw FHIR Data
Data Provenance
Clinical documents must have valid provenance
Schema Version
Schema version must be in format major.minor
Sections
Clinical Section Shape
Validation constraints for clinical document sections
Section Title
Section must have a title
Section Content
Section must have content
Section Code
Section code must be a valid LOINC code (e.g., 10154-3)
Section Order
Progress Note Shape
Additional constraints for progress notes
Encounter Date must be an xsd:date or an xsd:dateTime. FHIR's dateTime primitive permits date precision (YYYY, YYYY-MM, YYYY-MM-DD), so a source that stated only a calendar day must not be given an invented time; an untyped or xsd:string literal is not either type.
Encounter Date
Progress notes must specify the encounter date
Discharge Summary Shape
Additional constraints for discharge summaries
Document Date must be an xsd:date or an xsd:dateTime. FHIR's dateTime primitive permits date precision (YYYY, YYYY-MM, YYYY-MM-DD), so a source that stated only a calendar day must not be given an invented time; an untyped or xsd:string literal is not either type.
Document Date
Discharge summary must have a document date
Consultation Note Shape
Additional constraints for specialist consultation notes
Consultation note must not carry more than one encounter date
Laboratory Report Shape
Additional constraints for laboratory reports
Lab reports must have a document date
Imaging Report Shape
Additional constraints for imaging/radiology reports
Imaging reports must have a document date
Visit Summary Shape
Additional constraints for after-visit summaries
Visit summary must specify the encounter date
Medication Shape
Validation constraints for medication records
Drug Name
Medication must have a drug name
Dosage
Route
Frequency
Status
RxNorm Code
SNOMED Code
Medication records must have valid provenance
Prescriber
Indication
Course of Therapy Type
courseOfTherapyType should be acute, continuous, or unknown
As Needed (PRN)
Medication Form
Active Ingredient
Ingredient Strength
Provenance Class
Source FHIR Resource Type
Clinical Intent
Refills Allowed
Supply Duration Days
Dispensed Quantity
Prescription Category
Allergy Shape
Validation constraints for allergy/intolerance records
Allergen
Allergy must specify the allergen
Reaction
Severity
Severity must be mild, moderate, or severe
Criticality
Allergy Category
Lab Result Shape
Validation constraints for laboratory result records
Test Name
Lab result must have a test name
Value
Unit
Reference Range
Interpretation
Interpretation must be a code from the HL7 v3 ObservationInterpretation code system (http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation), a code from http://terminology.hl7.org/CodeSystem/data-absent-reason, or one of the retained legacy words. A source code in none of those is carried verbatim on clinical:interpretationSourceCode.
Interpretation Source Code
Interpretation source code must be a single string: the source's verbatim code, unmodified
LOINC Code
Condition Shape
Validation constraints for condition/diagnosis records
Condition Name
Condition must have a name
Clinical Status
Verification Status
Onset Date must be an xsd:date or an xsd:dateTime. FHIR's dateTime primitive permits date precision (YYYY, YYYY-MM, YYYY-MM-DD), so a source that stated only a calendar day must not be given an invented time; an untyped or xsd:string literal is not either type.
Onset Date
ICD-10 Code
Immunization Shape
Validation constraints for immunization records
Vaccine Name
Immunization must have a vaccine name
CVX Code
Lot Number
Site
Dose Quantity
Manufacturer
Procedure Shape
Validation constraints for procedure records
Procedure must have a name, as clinical:procedureName (canonical) or health:procedureName (deprecated import spelling, accepted during the clinical v1.15 migration window)
Procedure Name
Procedure name must be a single non-empty string
Procedure Name (deprecated spelling)
Procedure Date must be an xsd:date or an xsd:dateTime. FHIR's dateTime primitive permits date precision (YYYY, YYYY-MM, YYYY-MM-DD), so a source that stated only a calendar day must not be given an invented time; an untyped or xsd:string literal is not either type.
Procedure Date
Body Site
Performer
CPT Code
CPT code must be five characters: five digits (Category I), or four digits followed by F (Category II), T (Category III) or U (Proprietary Laboratory Analyses)
Procedure Name Spelling Shape
Warns that a record carries the deprecated health:procedureName spelling. Accepted during the clinical v1.15 migration window; removed with the window.
Procedure name is written on health:procedureName, which no Cascade vocabulary defines. Write clinical:procedureName instead: it is the property whose domain is clinical:Procedure and the one clinical:ProcedureShape names. Accepted during the clinical v1.15 migration window; this becomes a VIOLATION when the window closes.
Vital Sign Shape
Validation constraints for vital sign observations
Vital Type
Vital sign must have a valid type
Component 1 Value
Component 2 Value
Interpretation should be a code from the HL7 v3 ObservationInterpretation code system (http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation), a code from http://terminology.hl7.org/CodeSystem/data-absent-reason, or one of the retained legacy words. Carry a code the value sets do not contain verbatim on clinical:interpretationSourceCode and put the nearest ratified reading here. WARNING in clinical v1.15; this becomes a VIOLATION in a later version.
Device Name
Medication Use Episode Shape
Validation constraints for longitudinal medication episodes. Ensures source linkage and explainable status inference per Cascade Protocol requirements.
Canonical Name
Episode must have a canonical drug name
First Seen Date
Episode must have a first seen date (earliest clinical date from source records)
Last Seen Date
Episode must have a last seen date (most recent clinical date from source records)
Derived From Record
Episode MUST link to at least one source MedicationRecord (sourceRecordIds required per Cascade Protocol)
Every episode must trace back to its source records for explainability
Inferred Status
Episode MUST have an inferred status (active or inactive)
Status Reason
Episode MUST have a status reason explaining WHY system thinks this status (per No Silent Inference policy)
Enables answering: 'Why does system think this medication is active?'
Status Confidence
Episode must declare confidence level for status inference
Concept URI
Stable URI for the medication concept (RxNorm URI or minted Cascade URI)
Current Dose
Current Frequency
Current Route
Use Pattern
Therapeutic Class
Has Unresolved Conflicts
Flag indicating episode has data conflicts requiring user attention
Duration Days
Episode must have valid provenance (typically Reconciled for derived episodes)
Supplement Shape
Validation constraints for supplement records. Ensures regulatory status is always explicit per Cascade Protocol requirements.
Supplement Name
Supplement must have a name
Regulatory Status
Supplement MUST have explicit regulatory status to distinguish from FDA-approved medications
Required per Cascade Protocol to avoid implying clinical equivalence with prescription medications
Dose
Brand
Form
Evidence Strength
Level of clinical evidence supporting supplement use
Is Active
DSLD ID
NIH Dietary Supplement Label Database identifier
UPC
Cascade URI
Stable Cascade Protocol identifier (minted when no external ID exists)
Reason For Use
Social History Record Shape
Social History Category
SocialHistoryRecord requires a socialHistoryCategory from the defined value set
Packs Per Year
Alcohol Drinks Per Week
Occupation Title
Encounter Shape
Minimal validation constraints for clinical encounters (visits). Constrains cardinality, datatype and provenance; deliberately does not constrain what kind of visit an encounter may be.
A clinical:Encounter must be identified by an IRI so that clinical:hasEncounter edges can resolve to it
Encounter Class
Encounter Status
Encounter status should be one of the FHIR R4 EncounterStatus codes: planned, arrived, triaged, in-progress, onleave, finished, cancelled, entered-in-error, unknown
Encounter Type
Encounter Start must be an xsd:date or an xsd:dateTime. FHIR's dateTime primitive permits date precision (YYYY, YYYY-MM, YYYY-MM-DD), so a source that stated only a calendar day must not be given an invented time; an untyped or xsd:string literal is not either type.
Encounter Start
Encounter End must be an xsd:date or an xsd:dateTime. FHIR's dateTime primitive permits date precision (YYYY, YYYY-MM, YYYY-MM-DD), so a source that stated only a calendar day must not be given an invented time; an untyped or xsd:string literal is not either type.
Encounter End
Provider Name
Facility Name
Source Record ID
Encounter must declare exactly one valid cascade:dataProvenance
Encounter Temporal Shape
Encounter should carry a start, an end or an encounter date so that records linked to it can be placed in time
clinical:hasEncounter should reference a clinical:Encounter by IRI
Has Encounter Edge
clinical:indicationReference should reference the reason record (a Condition or Observation) by IRI
Indication Reference Edge
clinical:linkedCondition should reference a clinical:Condition by IRI
Linked Condition Edge
clinical:parsedIndicationReference should reference the matched reason record (a Condition or Observation) by IRI
Parsed Indication Reference Edge