TelemedicinePlatform Entity

v2.0.1
Service
Healthcare Services

Schema for telemedicine platforms providing remote healthcare services. Designed for AI agents to understand medical service capabilities, compliance requirements, and secure communication features.

Entity Hierarchy
TelemedicinePlatform
→
service
→
healthcare_services
→
telemedicine_platform

Format: @type → entityCategory → subcategory → entityType

4

Required Modules

2

Recommended Modules

12+

Functional Features

6

Site Actions

⭐ New Features in v2.0.1

entityCapabilities

Objective telemedicine platform capabilities with clear rules:

  • • camelCase (hasVideoConsultations, hasPatientRecords)
  • • Prefixes: has, is, accepts, supports
  • • Boolean values for objective verification
  • • Examples are expandable - no limits

siteCapabilities

Actions available on telemedicine platform with rules:

  • • snake_case (book_appointment, join_consultation)
  • • Based on verbs (what users can do)
  • • Only actually working actions
  • • Examples are expandable without limits
Required Modules
Essential modules for telemedicine platform entities
Required
auth

REQUIRED - Secure patient and provider authentication

Essential for HIPAA compliance and medical data protection

Required
security

REQUIRED - End-to-end encryption and data protection

Critical for protecting sensitive medical information

Required
compliance

REQUIRED - HIPAA, HITECH, and medical regulatory compliance

Mandatory for healthcare service platforms

Required
streaming

REQUIRED - Secure video conferencing for consultations

Core functionality for telemedicine services

Recommended Modules
Enhance telemedicine platform functionality and user experience
Recommended
payments
Recommended
notification
Entity Capabilities
Objective, verifiable telemedicine platform features and services. Define functional capabilities using camelCase naming with prefixes: "has", "is", "accepts", "supports".
Naming Convention Rules
  • • Use camelCase formatting (e.g., "hasVideoConsultations", "hasPatientRecords")
  • • Start with prefixes: "has", "is", "accepts", "supports"
  • • Examples shown below can be extended - no limitations on additional capabilities
  • • All values are boolean (true/false) for objective verification

Medical Services

hasVideoConsultations

Secure video calls with healthcare providers

hasAppointmentBooking

Schedule medical appointments online

hasPrescriptionManagement

Digital prescription services

hasRemoteMonitoring

Track patient health metrics remotely

Patient Management

hasPatientRecords

Secure electronic health records

hasSecureMessaging

HIPAA-compliant patient-provider messaging

hasInsuranceIntegration

Insurance verification and billing

hasEmergencyProtocols

Emergency response procedures

Platform Features

hasMultiLanguageSupport

Support for multiple languages

has24x7Support

Round-the-clock platform support

hasLabIntegration

Integration with laboratory services

hasPharmacyIntegration

Connection to pharmacy networks

Site Capabilities
Available actions for AI agents and automated systems. Define what users can actually do on your website using snake_case action names.
Action Naming Rules
  • • Use snake_case formatting (e.g., "book_appointment", "join_consultation")
  • • Actions should be verb-based describing what users can do
  • • Examples shown below are common patterns - extend with your specific actions
  • • List only actions that actually work on your website
book_appointment

Schedule consultations with healthcare providers

join_consultation

Enter secure video consultation sessions

access_records

View and manage medical records

send_secure_message

Communicate with healthcare providers securely

request_prescription

Request prescription renewals or new medications

pay_bills

Process medical billing and insurance claims

Schema Structure
TelemedicinePlatform entity schema definition
telemedicine_platform.json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "aimlVersion": "2.0.1",
  "schemaVersion": "2.0.1",
  "title": "TelemedicinePlatform Entity Schema",
  "description": "Schema for telemedicine platforms providing remote healthcare services",
  "type": "object",
  "properties": {
    "entityType": {
      "const": "telemedicine_platform",
      "description": "Entity type identifier"
    },
    "entityCategory": {
      "const": "service",
      "description": "Entity category"
    },
    "subcategory": {
      "const": "healthcare_services",
      "description": "Subcategory of service"
    },
    "name": {
      "oneOf": [
        { "type": "string" },
        { "$ref": "../components/multilingual-format.json#/$defs/LocalizedText" }
      ],
      "description": "Telemedicine platform name"
    },
    "description": {
      "oneOf": [
        { "type": "string" },
        { "$ref": "../components/multilingual-format.json#/$defs/LocalizedText" }
      ],
      "description": "Detailed description of the telemedicine platform"
    },
    "modules": {
      "type": "object",
      "description": "AIML modules used by this entity"
    },
    "properties": {
      "type": "object",
      "description": "Telemedicine platform specific properties",
      "properties": {
        "serviceTypes": {
          "type": "array",
          "items": { "type": "string" },
          "description": "Types of medical services offered"
        },
        "specializations": {
          "type": "array",
          "items": { "type": "string" },
          "description": "Medical specializations available"
        }
      }
    },
    "entityCapabilities": {
      "$ref": "../components/entity-capabilities-format.json#/$defs/EntityCapabilities",
      "description": "Objective capabilities and features of the entity"
    },
    "siteCapabilities": {
      "$ref": "../components/site-capabilities-format.json#/$defs/SiteCapabilities",
      "description": "Website capabilities and interaction features"
    }
  },
  "required": ["entityType", "entityCategory", "subcategory", "name", "description", "properties"],
  "allOf": [{ "$ref": "../base/service.json" }]
}
Complete Implementation Example
Real-world telemedicine platform entity with all v2.0.1 features
HealthConnect Virtual Care - Complete Schema
{
  "@context": "https://schemas.meta-aiml.org/v2.0.1/context.jsonld",
  "@id": "https://healthconnect.com/entity",
  "@type": "TelemedicinePlatform",
  "schemaVersion": "2.0.1",
  "entityType": "telemedicine_platform",
  "entityCategory": "service",
  "subcategory": "healthcare_services",

  "name": {
    "en": "HealthConnect Virtual Care",
    "es": "HealthConnect Atención Virtual"
  },
  "description": {
    "en": "Comprehensive telemedicine platform providing secure virtual consultations, remote monitoring, and digital health services with HIPAA-compliant infrastructure and 24/7 access to healthcare professionals."
  },
  "url": "https://healthconnect.com",
  "foundingDate": "2020-04-15",

  "properties": {
    "serviceTypes": ["virtual_consultations", "remote_monitoring", "digital_prescriptions", "health_coaching"],
    "specializations": ["primary_care", "mental_health", "dermatology", "cardiology", "endocrinology"],
    "operatingHours": "24/7",
    "averageWaitTime": "15 minutes",
    "supportedInsurance": ["medicare", "medicaid", "private_insurance"]
  },

  "modules": {
    "auth": {
      "version": "2.0.1",
      "enabled": true,
      "methods": ["secure_login", "two_factor", "biometric"],
      "providers": ["medical_id", "google", "apple"]
    },
    "security": {
      "version": "2.0.1",
      "enabled": true,
      "features": ["end_to_end_encryption", "secure_storage", "audit_logging"],
      "certifications": ["hipaa", "hitech", "gdpr"]
    },
    "compliance": {
      "version": "2.0.1",
      "enabled": true,
      "standards": ["hipaa", "hitech", "fda", "state_medical_boards"],
      "features": ["audit_trails", "consent_management", "data_retention"]
    },
    "streaming": {
      "version": "2.0.1",
      "enabled": true,
      "protocols": ["webrtc", "secure_streaming"],
      "features": ["hd_video", "screen_sharing", "recording"],
      "security": ["encrypted_streams", "secure_endpoints"]
    }
  },

  "entityCapabilities": {
    "functionalFeatures": {
      "hasVideoConsultations": true,
      "hasAppointmentBooking": true,
      "hasPatientRecords": true,
      "hasSecureMessaging": true,
      "hasPrescriptionManagement": true,
      "hasInsuranceIntegration": true,
      "hasRemoteMonitoring": true,
      "hasMultiLanguageSupport": true,
      "hasEmergencyProtocols": true,
      "has24x7Support": true
    },
    "contentTypes": ["medical_records", "prescriptions", "consultation_notes", "lab_results"],
    "businessModel": "telemedicine",
    "securityFeatures": ["hipaa_compliance", "end_to_end_encryption", "secure_storage"],
    "targetAudience": ["patients", "healthcare_providers", "medical_institutions"],
    "medicalServices": ["consultations", "diagnoses", "prescriptions", "monitoring"]
  },

  "siteCapabilities": {
    "availableActions": [
      "book_appointment", "join_consultation", "access_records",
      "send_secure_message", "request_prescription", "pay_bills"
    ],
    "interactionMethods": ["video_call", "secure_messaging", "mobile_app", "web_portal"],
    "contentAccess": ["patient_portal", "provider_portal"],
    "supportedDevices": ["desktop", "mobile", "tablet"],
    "languages": ["en", "es", "fr"],
    "realTimeFeatures": ["live_video", "instant_messaging", "real_time_monitoring"]
  }
}
Related Entities

Same Category (Service)

GenerativeAIPlatformBusinessServicesWebApp

Same Subcategory (Healthcare Services)

ClinicFitnessPlatform
← All EntitiesService Base →Streaming Module →Security Module →Try in Playground →