Chapter 2: Data Format Specification - Elder Profiles and Vital Signs

Standardized data formats form the bedrock of any interoperable technology ecosystem. Without common structures for representing information, systems cannot exchange data meaningfully, integration becomes impossibly complex, and the promise of seamless interoperability remains forever unfulfilled. The WIA-SENIOR-001 standard's Phase 1: Data Format Specification addresses this fundamental challenge by defining precise, comprehensive data structures for all information types generated, stored, and exchanged by elder care technology systems. This chapter explores the core data formats for elder profiles and vital signs monitoring, establishing the foundation upon which all other aspects of the standard build.

Data format standardization in healthcare presents unique challenges beyond those encountered in other domains. Health data must balance comprehensiveness with usability, supporting the rich complexity of human physiology and medical care while remaining practical for real-world implementation. Privacy and security considerations demand careful attention to which data elements systems collect and how they protect sensitive information. Regulatory compliance requirements from HIPAA, GDPR, FDA, and other authorities impose additional constraints. Cultural and linguistic diversity necessitates internationalization support. The WIA-SENIOR-001 data formats address all these challenges while maintaining elegance and implementability.

This chapter examines the two most fundamental data structures in elder care systems: the Elder Profile, which captures demographic, medical, and preference information about individual elders; and Vital Signs records, which document physiological measurements essential for health monitoring. Subsequent chapters explore additional data structures including alerts, medications, and activities. Together, these formats provide comprehensive coverage of all information flows in elder care technology ecosystems.

Design Principles for Elder Care Data Formats

Before examining specific data structures, understanding the principles that guided their design provides important context. The WIA-SENIOR-001 data formats embody six core design principles that balance competing requirements and ensure both technical excellence and practical utility.

Comprehensiveness

Elder care data formats must capture the full richness of information necessary for quality care delivery. Incomplete data structures force implementations to choose between omitting important information or adding proprietary extensions that break interoperability. The WIA-SENIOR-001 formats include extensive fields covering demographics, medical history, care preferences, vital signs with context, and metadata. Optional fields allow systems to include additional information when available without mandating complexity when unnecessary. This comprehensiveness ensures that standardized formats can represent real-world care scenarios without resorting to proprietary extensions.

Precision and Clarity

Ambiguous data formats lead to inconsistent implementations that cannot interoperate despite claiming standard compliance. Each field in WIA-SENIOR-001 formats includes precise definitions, required value types, allowed value ranges, and semantic meanings. Enumerated fields specify exact allowed values. Numeric fields document units, precision, and valid ranges. Date and time fields mandate ISO 8601 format. This precision eliminates ambiguity and ensures that different implementations interpret data identically.

Extensibility

Healthcare evolves continuously with new devices, measurements, conditions, and treatments. Data formats must accommodate future evolution without breaking existing implementations. WIA-SENIOR-001 formats include version fields enabling format evolution, optional data fields for future additions, and extension mechanisms for vendor-specific augmentation. Careful backward compatibility planning ensures that systems implementing newer format versions can still exchange data with older implementations, albeit potentially with reduced fidelity.

Cultural and Linguistic Sensitivity

Elder care is fundamentally human-centered, and data formats must respect human diversity. WIA-SENIOR-001 formats support 99 languages through UTF-8 encoding and explicit language specification. Cultural and religious preference fields enable culturally appropriate care. International address formats accommodate global deployment. Gender fields include options beyond binary male/female. This cultural sensitivity ensures the standard serves elders worldwide with respect for their identities and backgrounds.

Privacy by Design

Elder care data includes highly sensitive personal health information requiring protection. WIA-SENIOR-001 formats incorporate privacy-by-design principles, clearly marking fields containing Protected Health Information (PHI) or Personally Identifiable Information (PII). Separable data structures enable systems to isolate sensitive information for enhanced protection. Consent and authorization metadata supports granular access control. Explicit audit trail requirements ensure accountability for all data access and modifications.

Standards Alignment

Healthcare technology standards don't exist in isolation. WIA-SENIOR-001 deliberately aligns with established standards including HL7 FHIR, LOINC, SNOMED CT, RxNorm, and ICD-10, providing explicit mappings where applicable. This alignment enables integration with electronic health record systems, clinical decision support tools, and other healthcare IT infrastructure. Organizations can adopt WIA-SENIOR-001 without abandoning existing standards investments.

Table 2.1: Data Format Design Principles

Principle	Purpose	Implementation	Benefit
Comprehensiveness	Capture complete information	Extensive field coverage, optional fields	No proprietary extensions needed
Precision	Eliminate ambiguity	Exact definitions, types, ranges	Consistent interpretation
Extensibility	Support evolution	Versioning, optional fields, extensions	Future-proof design
Cultural Sensitivity	Respect diversity	99 languages, cultural preferences	Global applicability
Privacy by Design	Protect sensitive data	PHI marking, separable structures	Regulatory compliance
Standards Alignment	Interoperate broadly	FHIR mapping, standard vocabularies	Healthcare IT integration

The Elder Profile Data Structure

The Elder Profile serves as the central organizing structure in WIA-SENIOR-001 compliant systems, capturing comprehensive information about individual elders including demographics, medical history, care needs, preferences, and emergency contacts. This structure represents the "digital identity" of each elder in the care ecosystem, enabling personalized care delivery informed by complete knowledge of the individual's circumstances.

Elder Profiles comprise six major sections: identification and demographics, personal information including address, comprehensive medical information, care preferences and needs, emergency contacts, and audit metadata. Each section serves distinct purposes while contributing to a holistic representation of the elder's situation. The complete structure is represented in JSON format for ease of implementation, human readability, and broad programming language support.

Identification and Demographics

Every Elder Profile begins with a globally unique identifier (UUID) that serves as the permanent reference for that individual across all systems and data exchanges. This identifier must never change, even if other demographic information is corrected or updated. Following the UUID, demographic fields capture the elder's legal name (with separate first, middle, last, and optional suffix fields), date of birth in ISO 8601 format, gender (with options for male, female, other, and prefer-not-to-say to respect privacy and identity), and preferred language for communication specified using ISO 639-1 language codes.

An optional photo URL field allows systems to include a recent photograph of the elder, valuable for emergency responders, caregivers who may not know the elder personally, and facial recognition applications in some advanced systems. However, given the sensitive nature of photographs and potential privacy implications, this field remains optional and systems must obtain explicit consent before capturing or storing images.

{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "personalInfo": {
    "firstName": "Margaret",
    "middleName": "Ann",
    "lastName": "Johnson",
    "suffix": "",
    "dateOfBirth": "1945-06-15",
    "gender": "female",
    "language": "en",
    "photoUrl": "https://secure.example.com/photos/elder-123.jpg"
  }
}

Address Information

Comprehensive address information proves essential for emergency response, medication delivery, home care visits, and geographic analysis of care needs. The address structure supports international formats through separate fields for street address, city, state or province, postal code, and country using ISO 3166-1 country codes. Multiple address types (primary residence, alternate residence, billing address) can be associated with a single Elder Profile when necessary, though most implementations will use a single primary address.

"address": {
  "street": "742 Evergreen Terrace",
  "unit": "Apt 5B",
  "city": "Springfield",
  "state": "IL",
  "zipCode": "62701",
  "country": "US",
  "type": "primary-residence"
}

Medical Information

The medical information section of the Elder Profile captures health data essential for safe care delivery. This includes blood type (important for emergency care), known allergies (medications, foods, environmental), chronic conditions (diabetes, hypertension, COPD, etc.), current medications with dosages and schedules, primary physician contact information, and health insurance details. Each sub-field within medical information follows standardized vocabularies where applicable—medications use RxNorm codes, conditions use SNOMED CT or ICD-10 codes, and allergies use standardized allergy coding systems.

The chronic conditions array allows comprehensive documentation of pre-existing health issues that affect care plans and risk assessment. Each condition includes the condition name, diagnosis date, current status (active, in-remission, resolved), and optional severity indicator. This information enables care systems to contextualize vital signs and alerts appropriately—for example, slightly elevated blood pressure might be expected in someone with diagnosed hypertension, while the same reading in someone with no hypertension history could indicate developing illness.

"medicalInfo": {
  "bloodType": "A+",
  "allergies": [
    {
      "allergen": "Penicillin",
      "reaction": "Severe rash, difficulty breathing",
      "severity": "critical"
    },
    {
      "allergen": "Shellfish",
      "reaction": "Hives",
      "severity": "moderate"
    }
  ],
  "chronicConditions": [
    {
      "condition": "Type 2 Diabetes Mellitus",
      "snomedCode": "44054006",
      "diagnosisDate": "2010-03-15",
      "status": "active",
      "severity": "moderate"
    },
    {
      "condition": "Essential Hypertension",
      "snomedCode": "59621000",
      "diagnosisDate": "2008-11-20",
      "status": "active",
      "severity": "mild"
    }
  ],
  "primaryPhysician": {
    "name": "Dr. Sarah Mitchell",
    "specialty": "Geriatric Medicine",
    "phone": "+1-555-0123",
    "email": "dr.mitchell@example.com"
  }
}

Care Preferences and Needs

Care preferences and needs capture information about the elder's functional status, care requirements, and personal preferences that guide care delivery. Mobility level uses standardized categories (independent, needs-assistance, walker, wheelchair, bedridden) that inform safety protocols and care planning. Cognitive level similarly categorizes cognitive function (normal, mild-impairment, moderate-impairment, severe-impairment, dementia) enabling appropriate communication strategies and monitoring approaches.

Communication preferences specify the elder's preferred methods and times for contact, important for systems that send reminders, alerts, or wellness checks. Activity preferences document hobbies, interests, and enjoyable activities, valuable for social engagement programming and mental health support. Dietary restrictions capture both medical needs (diabetic diet, low-sodium) and personal preferences (vegetarian, kosher, halal), ensuring culturally and medically appropriate meal planning. Religious and cultural preferences guide respectful care delivery aligned with the elder's values and traditions.

"carePreferences": {
  "mobilityLevel": "needs-assistance",
  "mobilityAids": ["walker", "cane"],
  "cognitiveLevel": "mild-impairment",
  "communicationPreferences": {
    "preferredContactMethods": ["phone", "email"],
    "bestTimeToContact": "09:00-11:00, 14:00-16:00",
    "languageAssistanceNeeded": false
  },
  "activityPreferences": [
    "Reading",
    "Gardening",
    "Classical music",
    "Card games",
    "Nature documentaries"
  ],
  "dietaryRestrictions": [
    "Diabetic diet",
    "Low sodium",
    "No shellfish (allergy)"
  ],
  "religiousCulturalPreferences": [
    "Christian - attends services Sunday mornings",
    "Prefers female caregivers when available"
  ]
}

Emergency Contacts

Comprehensive emergency contact information ensures that care systems can reach family members, friends, or other designated individuals in urgent situations. The emergency contacts array allows multiple contacts with priority ordering—primary contact, secondary contact, etc. Each contact includes name, relationship to elder, phone numbers (mobile, home, work), email address, and physical address. An optional "authorized for medical decisions" flag identifies contacts empowered to make healthcare decisions if the elder is incapacitated, critical information for emergency situations requiring immediate treatment decisions.

"emergencyContacts": [
  {
    "priority": 1,
    "name": "Robert Johnson",
    "relationship": "Son",
    "phoneMobile": "+1-555-0199",
    "phoneHome": "+1-555-0188",
    "email": "robert.johnson@example.com",
    "address": "123 Maple Street, Springfield, IL 62702",
    "authorizedForMedicalDecisions": true,
    "notes": "Lives 10 minutes away, available 24/7"
  },
  {
    "priority": 2,
    "name": "Jennifer Davis",
    "relationship": "Daughter",
    "phoneMobile": "+1-555-0177",
    "email": "jennifer.davis@example.com",
    "address": "456 Oak Avenue, Chicago, IL 60601",
    "authorizedForMedicalDecisions": true,
    "notes": "Lives in Chicago, prefers text messages"
  }
]

Vital Signs Data Structure

Vital signs monitoring forms the cornerstone of technology-enabled elder care, providing objective physiological measurements that reveal health status, detect deterioration, and guide interventions. The WIA-SENIOR-001 Vital Signs data structure captures comprehensive measurements including heart rate, blood pressure, temperature, oxygen saturation, respiratory rate, weight, and blood glucose, along with essential metadata about measurement context, timing, and abnormality detection.

Each vital signs record represents a single measurement event at a specific point in time. The structure includes a timestamp in ISO 8601 format (always in UTC to avoid timezone complications), a reference to the elder being measured via their UUID, and individual measurement objects for each vital sign type. Separating each vital sign into its own object with dedicated fields for value, unit, and abnormality status enables precise representation while supporting implementations that may not measure all vital signs at every measurement event.

Heart Rate Measurement

Heart rate (pulse) measurement includes the beats per minute (bpm) value, rhythm characterization (regular or irregular), and an abnormality flag. The normal heart rate range for older adults typically falls between 60-100 bpm, though individual baselines vary. The rhythm field captures whether the pulse is regular (consistent intervals between beats) or irregular (varying intervals), with irregular rhythms potentially indicating atrial fibrillation or other arrhythmias requiring medical attention. The isAbnormal flag is set based on age-appropriate norms and individual baseline comparisons when available.

{
  "timestamp": "2025-01-15T08:30:00Z",
  "elderId": "123e4567-e89b-12d3-a456-426614174000",
  "heartRate": {
    "bpm": 72,
    "rhythm": "regular",
    "isAbnormal": false,
    "measurementMethod": "wearable-sensor"
  }
}

Blood Pressure Measurement

Blood pressure combines systolic and diastolic pressures, both measured in millimeters of mercury (mmHg). Systolic pressure (the higher number) represents pressure when the heart contracts and pumps blood; diastolic pressure (the lower number) represents pressure when the heart relaxes between beats. Blood pressure classification for older adults follows established guidelines: normal is less than 120/80 mmHg, elevated is 120-129 systolic with diastolic less than 80, stage 1 hypertension is 130-139 systolic or 80-89 diastolic, and stage 2 hypertension is 140 or higher systolic or 90 or higher diastolic. The abnormality flag triggers for readings outside normal range, though some elders with controlled hypertension may have slightly elevated baseline pressures.

"bloodPressure": {
  "systolic": 128,
  "diastolic": 82,
  "unit": "mmHg",
  "isAbnormal": false,
  "measurementMethod": "automated-cuff",
  "position": "seated",
  "armUsed": "left"
}

Table 2.2: Vital Signs Normal Ranges and Abnormality Thresholds

Vital Sign	Normal Range (Elders)	Abnormal Low	Abnormal High
Heart Rate	60-100 bpm	< 60 bpm	> 100 bpm
Blood Pressure	< 120/80 mmHg	< 90/60 mmHg	≥ 140/90 mmHg
Temperature (Oral)	36.5-37.5°C	< 36.0°C	> 38.0°C
Oxygen Saturation	95-100%	< 95%	N/A
Respiratory Rate	12-20 breaths/min	< 12 breaths/min	> 20 breaths/min
Blood Glucose (Fasting)	70-100 mg/dL	< 70 mg/dL	> 100 mg/dL

Temperature, Oxygen Saturation, and Respiratory Rate

Temperature measurement includes the numeric value, unit (Celsius or Fahrenheit), measurement location (oral, temporal, axillary, tympanic), and abnormality indicator. Measurement location matters significantly—temporal (forehead) readings typically run about 0.5°C lower than oral readings, while axillary (armpit) readings run about 0.5-1°C lower than oral. Normal oral temperature for adults ranges from 36.5-37.5°C (97.7-99.5°F), with fever generally defined as 38°C (100.4°F) or higher. Hypothermia concerns arise below 36°C (96.8°F).

Oxygen saturation (SpO2) measures the percentage of hemoglobin in blood saturated with oxygen, crucial for detecting respiratory problems. Normal oxygen saturation should be 95-100%, with readings below 95% indicating hypoxemia that may require supplemental oxygen. Chronic lung conditions like COPD may result in slightly lower baseline oxygen saturations (90-94%), which systems should consider when determining abnormality. Respiratory rate counts breaths per minute, with normal adult range of 12-20 breaths per minute. Tachypnea (rapid breathing over 20 breaths/minute) may indicate respiratory distress, fever, pain, or anxiety, while bradypnea (slow breathing under 12 breaths/minute) might suggest medication effects or neurological issues.

Weight and Blood Glucose

Weight tracking enables monitoring for concerning trends including rapid weight loss (possible indication of illness, depression, or eating difficulties) or rapid weight gain (possible indication of fluid retention from heart failure). Weight includes value, unit (kg or lbs), and optional date of measurement when weight is not measured synchronously with other vitals. Significant weight changes—typically defined as 5% or more in a month or 10% in six months—warrant clinical attention.

Blood glucose monitoring is particularly important for elders with diabetes or prediabetes. Blood glucose includes value, unit (mg/dL or mmol/L), measurement context (fasting, post-meal, random), and abnormality flag. Normal fasting glucose ranges from 70-100 mg/dL, while post-meal glucose should remain below 140 mg/dL. Hypoglycemia (low blood sugar below 70 mg/dL) represents a medical emergency requiring immediate treatment, while persistent hyperglycemia (high blood sugar) indicates poor diabetes control requiring medication or lifestyle adjustments.

"temperature": {
  "value": 36.8,
  "unit": "celsius",
  "location": "oral",
  "isAbnormal": false
},
"oxygenSaturation": {
  "percentage": 97,
  "isAbnormal": false,
  "measurementMethod": "pulse-oximeter"
},
"respiratoryRate": {
  "breathsPerMinute": 16,
  "isAbnormal": false
},
"weight": {
  "value": 68.5,
  "unit": "kg",
  "measurementDate": "2025-01-15"
},
"bloodGlucose": {
  "value": 105,
  "unit": "mg/dL",
  "measurementContext": "fasting",
  "isAbnormal": true,
  "note": "Slightly elevated, consistent with prediabetes diagnosis"
}

Data Validation and Quality Assurance

Standardized data formats require rigorous validation to ensure data quality and prevent errors that could compromise care delivery. WIA-SENIOR-001 specifies comprehensive validation rules that compliant systems must enforce when creating or modifying Elder Profiles and Vital Signs records.

Required Field Validation

Certain fields are mandatory and systems must reject records that omit them. Elder Profiles require UUID, first name, last name, date of birth, and at least one emergency contact. Vital Signs records require timestamp, elder ID reference, and at least one vital sign measurement. Attempting to create records without required fields must result in clear error messages identifying the missing information.

Data Type and Format Validation

Each field has a specified data type and format that systems must validate. UUIDs must conform to UUID format specifications. Dates and timestamps must use ISO 8601 format. Numeric fields must contain valid numbers within specified ranges—heart rate between 30-200 bpm, systolic blood pressure between 60-300 mmHg, temperature between 35-42°C or 95-108°F. Email addresses must match valid email format. Phone numbers should follow E.164 international format. Language codes must be valid ISO 639-1 codes. Country codes must be valid ISO 3166-1 codes.

Referential Integrity

Vital Signs records reference Elder Profiles via UUID in the elderId field. Systems must validate that referenced elder IDs correspond to existing Elder Profiles, rejecting vital signs records for non-existent elders. When Elder Profiles are deleted, systems must handle associated vital signs records appropriately—either preventing deletion until dependent records are removed, automatically deleting associated records (cascade delete), or archiving the profile while maintaining vital signs for historical analysis.

Value Range Validation

Numeric vital signs measurements must fall within physiologically plausible ranges even if abnormal. Heart rate between 30-200 bpm covers the range from severe bradycardia to extreme tachycardia beyond which measurement accuracy is questionable. Blood pressure systolic 60-300 mmHg and diastolic 40-200 mmHg cover ranges from severe hypotension to hypertensive crisis. These validation ranges prevent data entry errors (like typing 720 instead of 72 for heart rate) while accepting extreme but physiologically possible values that might occur in medical emergencies.