Health Data Consent Manager

{
  "service_type": "platform",
  "base_url": "https://ndhm.gov.in",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "Government of India initiative (National Digital Health Mission / Ayushman Bharat Digital Mission). No public consumer pricing; likely free for citizens/patients. Implementation and integration costs may apply for healthcare providers and health tech companies."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Health information aggregation for individuals",
    "Consent management for health data exchange",
    "Fetching health records from one or more Health Information Providers",
    "National digital health ecosystem (India) participation",
    "Health data interoperability across providers",
    "Patient-controlled data sharing via consent artifacts",
    "Integration with healthcare providers, HIUs, and HIPs under ABDM"
  ],
  "raw_analysis": "The National Digital Health Mission (NDHM), now operating under the Ayushman Bharat Digital Mission (ABDM), is a Government of India initiative to build a national digital health ecosystem. The 'Health Data Consent Manager' role described here corresponds to a Health Information User (HIU) / Consent Manager within the ABDM architecture, enabling patients to consent to and fetch their health records from multiple Health Information Providers (HIPs) through a federated, interoperable framework. The platform is not a conventional commercial SaaS; it is a public digital infrastructure. While there is no public self-serve REST API documented on the main portal, ABDM does publish developer resources, sandbox environments, and specifications (e.g., via sandbox.abdm.gov.in and the ABDM Sandbox) for integrating building blocks such as the Consent Manager, Health Information Exchange & Consent Manager (HIE-CM), and the Unified Health Interface (UHI). Authentication across these APIs typically relies on certificates, OAuth-based flows, and consent artefacts using standards like HL7 FHIR. The service is highly relevant for health tech companies, hospitals, clinics, laboratories, and insurers operating in India. It is mature in the sense of being a national-scale program with active policy backing, though integration complexity and regulatory compliance (Data Protection Bill/DPDP Act) are significant considerations. Pricing is not consumer-facing; participation may be free or involve compliance and technical integration costs."
}

0/3 tests passed

```json
{
  "overall": 38,
  "dimensions": {
    "token_efficiency": 6.5,
    "first_try_success": 3.0,
    "response_parseability": 4.5,
    "error_clarity": 4.0,
    "doc_quality": 5.0,
    "auth_simplicity": 3.0,
    "latency": 1.0,
    "consistency": 2.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "Government of India initiative (ABDM/NDHM). Likely free for citizens; integration costs for providers and health tech companies. No public consumer pricing."
  },
  "issues": [
    "Website unreachable — all three connectivity checks (uptime, robots.txt, llms.txt) failed with connection errors",
    "No llms.txt or robots.txt accessible, preventing agent-friendly discovery",
    "High latency on failed connection attempts (~3s timeouts)",
    "Platform is India-specific government health infrastructure — limited relevance for most users outside that ecosystem",
    "No public API documentation surfaced through these checks",
    "Onboarding likely involves ABDM registration, consent artifacts, and provider integration — not minutes-scale",
    "Pricing model unclear, making it hard to recommend with confidence"
  ],
  "recommendations": [
    "Publish a stable, reachable website with uptime monitoring and a status page",
    "Add llms.txt and robots.txt to enable agent discoverability",
    "Provide clear public documentation on consent flows, HIP/HIU integration, and sandbox access",
    "Clarify pricing and eligibility (who can use it, what's free, what costs)",
    "Improve response latency well below 500ms for API endpoints",
    "Offer a magic-link / NotLogin-style onboarding path to reduce human signup friction",
    "Add structured JSON exports for consent artifacts and health records to improve agent parseability"
  ]
}
```