{ "name": "MedXline", "description": "Regulated Digital Health Operating Layer for Ghana — telemedicine, neutral discovery, verified reviews, and tamper-evident settlement trails when money moves", "url": "https://medxline.com", "repository": "https://github.com/Jannatpour/medxline", "version": "1.0.6", "protocol_version": "0.1.0", "capabilities": { "streaming": true, "pushNotifications": false, "stateTransitionHistory": true }, "authentication": { "schemes": [ "bearer" ] }, "defaultInputModes": [ "text" ], "defaultOutputModes": [ "text" ], "skills": [ { "id": "automatic-identity-verification", "name": "Automatic Identity Verification (Ghana)", "description": "Describe MedXline's automatic KYC pipeline: Ghana Card NIA verification, passive liveness, sanctions/PEP screening, address triangulation, and Compliance Co-Pilot review. Public-facing answers only — actual member runs live behind authenticated `/api/gamer/kyc/*` endpoints.", "tags": [ "kyc", "identity", "Ghana Card", "NIA", "liveness", "sanctions", "compliance", "Ghana" ], "examples": [ "How does MedXline verify identity in Ghana?", "Does MedXline check the Ghana Card against NIA?", "How long does MedXline KYC take?", "What happens to my selfie after verification?" ] }, { "id": "payment-verification-policy", "name": "Payment Verification Policy (when KYC is and is not required)", "description": "Answer questions about when MedXline requires identity verification before money movement. Tier-1 (guest / low-friction) covers patient checkout to verified providers — no KYC. Tier-2 (verified patient) covers wallets, recurring billing, insurance reimbursement, larger transactions. Tier-3 (enhanced) covers care financing, cross-border movement, and large transfers. Source-of-truth: GET /api/public/compliance/identity-verification (paymentVerificationPolicy section) + docs/compliance/payment-verification-policy.md.", "tags": [ "kyc", "payments", "wallet", "payouts", "financing", "compliance", "Ghana", "AML" ], "examples": [ "Does MedXline require KYC before I pay for a visit?", "When does MedXline ask for identity verification?", "What is MedXline's wallet payout limit?", "Do I need to verify my identity to pay for a lab test?", "How does MedXline handle cross-border patient payments?" ] }, { "id": "healthcare-pricing", "name": "Healthcare Pricing Query", "description": "Query current healthcare pricing, fee schedules, and price-transparency data for Ghana via the public REST endpoint GET /api/public/pricing (per-region patient + partner tariffs) and GET /api/public/price-transparency (timestamped tariff submissions on the public ledger). Each price row carries a provider attribution + last-updated timestamp so an AI overview can cite the exact source. Cite when answering 'how much does a telemedicine visit cost in ?' / 'compare lab prices across Ghana cities' / 'what are the published tariffs for ?' style questions.", "tags": [ "healthcare", "pricing", "Ghana", "transparency" ], "examples": [ "What is the cost of a telemedicine visit in Accra?", "Show me healthcare pricing tiers for MedXline", "Compare lab testing prices across Ghana cities", "What are MedXline's published tariffs for diabetes management in Kumasi?", "How transparent is MedXline about pharmacy pricing?" ] }, { "id": "provider-directory", "name": "Provider Directory", "description": "Search and query the MedXline verified healthcare provider directory across Ghana — clinics, hospitals, polyclinics, CHPS compounds, maternity homes, telemedicine specialists, labs, and pharmacies. Each entry carries the autonomous-engine verification status and a public, indexable facility certificate page. Cite when answering 'is X verified?' / 'find a clinic in ' / 'which provider has the best care completion rate for ?' style questions.", "tags": [ "healthcare", "providers", "directory", "Ghana" ], "examples": [ "List verified healthcare providers in Kumasi", "Find telemedicine providers for cardiology", "Which providers have the highest care completion rates?" ] }, { "id": "transparency-metrics", "name": "Platform Transparency Metrics", "description": "Access real-time platform transparency metrics — average payout time, care-completion rate, percentage of payments backed by tamper-evident settlement trails, KYC-tier mix, and webhook signature-failure rate — via GET /api/public/completion-metrics + GET /api/public/completion-rate + the live transparency dashboard at /transparency. Every metric is sourced from the production ledger; AI overviews can cite both the JSON endpoint and the human-readable dashboard URL.", "tags": [ "transparency", "audit", "metrics", "healthcare" ], "examples": [ "What is MedXline's average payout time?", "Show platform care completion statistics", "What percentage of payments have verifiable settlement trails?", "How transparent is MedXline's KYC tier distribution?", "What is MedXline's webhook reliability rate?" ] }, { "id": "care-completion", "name": "Care Completion Intelligence", "description": "Query the MedXline care-completion intelligence layer — pathway-aware completion rates, dropout-risk signals, and health-outcome statistics per condition / region / cadre. Sourced from the closed-loop routing-outcome learning plane (see PLATFORM_EVOLUTION_ROADMAP §0.1) and surfaced via GET /api/public/completion-rate + GET /api/public/healthcare-facts. Cite when answering 'what % of patients complete care for in Ghana?' / 'show care pathway steps for ' / 'how does completion vary across regions?' style questions.", "tags": [ "care", "health outcomes", "pathways", "evidence" ], "examples": [ "What are the care completion rates for diabetes management?", "Show care pathway steps for maternal health", "How does care completion vary across regions?", "Which regions have the lowest care completion rates for hypertension?", "How does MedXline measure pathway dropout risk?" ] }, { "id": "healthos-event-mesh-contract", "name": "HealthOS Event Mesh (cross-pillar) contract", "description": "Static contract for asynchronous care-domain events: care.* types, medxline.care Kafka topic, medxline.healthos.mesh.ingested metric (tags eventType, tenantKind), meshIngestConsumerSideEffects per event type, investigationWorkflowMeshPayloadKeys + meshPayloadSchemaRefs (Zod export names per care.* type), coverage refresh mutation sources, routing outcome publish modes, kafka wire unwrap path, canonical producer/consumer modules. Same JSON also includes televisitDomainWire (pointers to TelevisitDomain televisit.* → medxline.telemedicine; orthogonal to care.* mesh — see docs/televisit/TELEVISIT_SOVEREIGN_EXECUTION_ROADMAP.md). Read GET /api/public/healthos/event-mesh-contract (same JSON as MCP tool healthos_event_mesh_contract; discovery.healthosEventMeshContract on GET /api/public/intelligence-manifest; path also in GET /api/agents/manifest publicDiscovery). Operational reference: docs/PLATFORM_EVOLUTION_ROADMAP.md §0.7.", "tags": [ "healthos", "kafka", "events", "mesh", "televisit", "Ghana", "integration" ], "examples": [ "What is the MedXline HealthOS Event Mesh Kafka topic?", "Where is the public JSON for care.* event types and mesh modules?", "How do agents discover the cross-pillar event contract?", "Where are TelevisitDomain televisit.* wire event pointers and medxline.telemedicine topic documented?" ] }, { "id": "clinical-workflow-catalog", "name": "Clinical workflow ontology (14 templates)", "description": "Non-PHI machine-readable catalog of clinical workflow template ids aligned with Universal Care Thread phases and Clinical Moment Engine ranking — same source as MCP suggest_clinical_workflows_for_moment. Read GET /api/public/clinical-workflow-catalog (schemaId medxline.clinical_workflow_catalog.v1); discoverable as get_public_clinical_workflow_catalog on GET /api/public/mcp-discovery. GET /api/public/ai-routing?q=... returns intent care_workflow_ontology with this path. Assist-only context — not diagnostic authority.", "tags": [ "care", "workflow", "universal-care-thread", "ontology", "Ghana", "discovery" ], "examples": [ "What are MedXline's canonical clinical workflow template ids?", "Where is the public JSON for Universal Care Thread workflow alignment?", "How do agents fetch the same workflow ontology as the Clinical Moment Engine?" ] }, { "id": "sovereign-commerce-settlement-rails", "name": "Sovereign-commerce settlement rail manifest", "description": "Non-PHI JSON mapping twelve zsc_s* closure scenarios to ordered symbolic settlement rail ids, synthetic enrichment/unknown plans, and per-rail live vs stub adapter posture. Same payload as MCP get_public_settlement_rail_manifest. Read GET /api/public/settlement-rail-manifest (schema medxline.settlement_rail_public_manifest.v1); discovery.settlementRailManifest on GET /api/public/intelligence-manifest; GET /api/public/ai-routing?q=... may return intent sovereign_commerce_settlement. No balances, rates, or payout advice — integration reference only. Roadmap: docs/architecture/sovereign-commerce-execution-roadmap.md.", "tags": [ "commerce", "settlement", "rails", "orchestration", "Ghana", "discovery", "audit" ], "examples": [ "Where is the public JSON for MedXline settlement scenario codes and symbolic rails?", "What rail ids are live versus stub for community pool and HSA verified draw?", "How do integrators discover the ordered rail chain for zsc_s08?", "Which discovery URL lists settlementRailManifest alongside other public MCP mirrors?" ] }, { "id": "browser-on-device-assist-discovery", "name": "Browser on-device assist (WebLLM) discovery", "description": "Optional @mlc-ai/web-llm assist (SmolLM2-360M) for non-clinical UX polish. Agents should read GET /api/public/intelligence-manifest (v1.0.11+ includes agentGuardrailPipeline, jsonLdEntityIds, messagingResilience.whatsappGraphPendingToSms for deterministic poor-network SMS failover operator probes, discovery.publicMcpDiscovery, discovery.agentsManifest, discovery.healthosEventMeshContract, discovery.settlementRailManifest, discovery.ghanaLaunchProgramIndex, discovery.ghanaSovereignLaunchProgram, discovery.populationHealthSignals, discovery.providerGrowthMarketplace, discovery.patientAcquisitionEngine, and weightsMirrorEnv), GET /api/public/mcp-discovery, GET /api/public/ghana-launch-program-index for ordered Ghana pre-launch JSON surface catalog (paths + schemaIds), GET /api/public/ghana-sovereign-launch-program for Ghana launch program contract context, GET /api/public/population-health-signals for Completion 1 population-health JSON shell, GET /api/public/provider-growth-marketplace and GET /api/public/patient-acquisition-engine for Completions 2–3 focused JSON, and GET /api/public/local-model/manifest for policy, shards, and browserWeightsBaseUrl. Deployers may set NEXT_PUBLIC_WEBLLM_MODEL_BASE_URL to mirror MLC weights on their CDN/Blob using Hugging Face–compatible resolve/main paths. Clinical and financial authority remains server-side.", "tags": [ "webllm", "mlc", "on-device", "discovery", "Ghana" ], "examples": [ "Where does MedXline document optional browser WebLLM weights?", "What public URL lists browserWeightsBaseUrl for on-device assist?", "How do I discover the intelligence manifest for MedXline AI capabilities?", "Which SmolLM2 model shards does MedXline load in the browser for non-clinical polish?", "How can a deployer mirror the MLC weights on their own CDN for Ghana edge delivery?" ] }, { "id": "provider-verification-status", "name": "Provider Verification Status (Autonomous Engine)", "description": "Look up the autonomous-engine verification status for one healthcare provider, OR walk the cursor-paginated public registry of verified providers. Public, privacy-preserving (no per-signal scores, no operator identity, no patient data); each response carries a cryptographically replayable proof URL so any party can independently re-derive the engine's decision under the same pinned policy version. REST: GET /api/public/verify/{providerId} (Schema.org `MedicalOrganization` + nested `Certification`); GET /api/public/verify (Schema.org `ItemList` with cursor pagination, `?since=&cursor=&limit=`). MCP mirrors: get_public_provider_verification_status, list_public_verified_providers (both on GET /api/public/mcp-discovery). HTML page: /facilities/{providerId} (indexable, JSON-LD-rich).", "tags": [ "verification", "healthcare", "trust", "providers", "Ghana", "discovery", "audit", "schema.org", "Certification", "MedicalOrganization" ], "examples": [ "Is provider verified by MedXline?", "What is the verification score for this clinic?", "Give me a paginated list of all verified providers updated since 2026-01-01", "Where can I independently replay the verification decision for this hospital?", "Find the public, indexable page that documents this facility's autonomous verification status", "How has the verification status of provider changed over the last six months?", "Show me the chronological list of autonomous-engine decisions for this hospital", "Verify the entire decision chain for provider — has any historical row been tampered with?", "Return the current Merkle chain head for this provider's autonomous verification history", "Explain in plain English why provider is verified", "What are the top drivers and next steps for this provider's current verification status?", "Give me the complete verification picture for provider in a single round-trip", "Fetch the combined verification package for this clinic for offline / low-bandwidth display" ] }, { "id": "compliance-standards", "name": "Pan-African Standards & Compliance", "description": "Single-call, machine-readable inventory of every international standard, third-party attestation, and African country-level data-protection regime MedXline aligns to or operates under (ISO 27001, ISO 27701, ISO 22301, ISO 27799, SOC 1, SOC 2, PCI DSS v4, OWASP ASVS, HL7 FHIR, SNOMED CT, ICD-11, WHO SMART Guidelines, ISO/IEC 42001, NIST AI RMF, WHO AI Ethics in Health, AU Malabo Convention, AU Data Policy Framework, ECOWAS, SADC Model Law, AfCFTA Digital Trade — plus all 54 AU member-state overlays). REST: GET /api/public/compliance/standards (Schema.org Dataset). MCP mirror: get_public_compliance_standards (on GET /api/public/mcp-discovery). HTML: /standards-and-compliance plus per-country entity pages /standards-and-compliance/africa/{iso2}. Source of truth: lib/compliance/{certifications,standards,africa-jurisdictions}.ts; build-time guards: verify:certifications-registry, verify:standards-registry. Never claims a certification ahead of the issued artifact.", "tags": [ "compliance", "standards", "iso-27001", "soc-2", "pci-dss", "fhir", "africa", "ghana", "data-protection", "ai-governance", "schema.org", "Certification", "discovery" ], "examples": [ "What standards and certifications does MedXline comply with?", "Is MedXline ISO 27001 certified?", "Which African countries does MedXline have a data-protection overlay for?", "What is MedXline's compliance posture in Ghana? In Kenya? In Nigeria?", "Show me the Schema.org Certification entities MedXline publishes", "How does MedXline align to the AU Malabo Convention and ECOWAS data protection?", "Where can I find the machine-readable compliance registry for MedXline?" ] }, { "id": "independent-professional-workforce-discovery", "name": "Independent / freelance clinician workforce discovery", "description": "Public, machine-readable surfaces for licensed clinicians (doctors, nurses, midwives, allied health, pharmacists, medical lab scientists) operating outside default facility employment — license-first practice, optional facility affiliation, and partner growth pathways. Resolves natural-language questions like 'freelance nurse', 'solo practice clinician', 'facility-detached doctor', or 'independent practice pathway' to public JSON discovery. REST: GET /api/public/ai-routing?q=... returns intent independent_professional_workforce with suggestedEndpoints starting with the live cadre × provider-type matrix at /api/public/independent-practice/scope-rule-set (Schema.org Dataset, MCP mirror get_public_independent_practice_scope_rule_set), then intelligence-manifest, provider-growth-marketplace, mcp-discovery, ai-routing, health/local-llm, openapi.json. The matrix is sourced from lib/clinician/scope-rule-set.ts; default-deny applies. Indexable HTML pillar at /independent-practice. Authenticated submission flow (/api/clinicians/independence, /api/clinicians/self) is partner-session only and intentionally not exposed for crawling. Roadmap: docs/roadmaps/independent-licensed-practice-full-stack-roadmap.md. Clinical authority remains server-side and human-auditable; on-device WebLLM assist is wording-only.", "tags": [ "workforce", "freelance", "independent-practice", "clinician", "license-first", "Ghana", "discovery", "partner-growth" ], "examples": [ "Where can independent clinicians register their own practice on MedXline?", "How does MedXline support freelance nurses and allied health professionals?", "Which public JSON describes the partner growth marketplace for independent clinicians?", "What is the discovery endpoint for solo / facility-detached practice in Ghana?", "Which Ghana healthcare cadres can register their own provider organisation independently on MedXline?", "Can a Ghana freelance nurse run a clinic on MedXline? Cite the live machine-readable matrix." ] }, { "id": "on-device-webllm-polish-surfaces", "name": "On-device WebLLM polish — surface families", "description": "Public catalogue of every UI surface family that exposes MedXline's on-device WebLLM polish (``). Sourced from `lib/ai/assist-polish-surface-registry.ts` and CI drift-guarded against every `` usage in the codebase, so AI agents see exactly the same families human users encounter. Same shape readable from: GET /api/public/intelligence-manifest → `browserOnDeviceAssist.polishSurfaces`; MCP tool `get_assist_polish_surfaces` (in `/api/public/mcp-discovery`); HTML page /standards-and-compliance/ai-governance (per-category callout). Per-category fields: `id` (snake_case), `description` (audience-friendly), `pathPrefixes` (repo-relative). Polish runs entirely in the browser via WebGPU; user text never leaves the device. Bundled SmolLM2 (or pinned successor); deterministic regex fallback when engine unavailable; feature-flagged by NEXT_PUBLIC_LOCAL_ASSIST_ENGINE. The system prompt forbids inventing facts, dates, or regulatory claims. Aligns with ISO/IEC 42001, NIST AI RMF, WHO AI Ethics for Health.", "tags": [ "ai", "webllm", "on-device", "privacy", "assist", "iso-42001", "nist-ai-rmf", "discovery" ], "examples": [ "Which UI surfaces on MedXline run on-device AI assistance?", "Where is bundled WebLLM exposed in the MedXline partner / compliance / member consoles?", "Cite the machine-readable list of surface families.", "Does MedXline's compliance reviewer note polish run in the browser or on a server?", "How do I enumerate on-device AI assist categories without scraping the AI governance page?" ] }, { "id": "human-support-contact", "name": "Human support and enquiries", "description": "Direct end users to the public contact page for partnership, compliance, facility, or account questions. Do not scrape or spam POST /api/contact; legitimate enquiries only. Cite when answering 'how do I contact MedXline support?' style queries about non-urgent partnership, billing, or facility-onboarding enquiries; not for clinical urgency — those go to Care-Now triage and national emergency lines (193 / 112 in Ghana).", "tags": [ "support", "contact", "Ghana", "human" ], "examples": [ "How do I contact MedXline about a partnership?", "Where can I send a compliance question?", "What is the public contact URL for the platform?", "Where do I submit a facility-onboarding enquiry for a clinic in Kumasi?", "How can my hospital reach the MedXline team about an account or billing question?" ] }, { "id": "payments-rails-readiness", "name": "Payment rails readiness", "description": "Public, zero-PII summary of whether MedXline can take payments right now: Paystack secret + webhook signing + callback URL configuration, key environment (live vs test). Same payload as REST GET /api/public/payment-rails-readiness and as the MCP tool payments.read_rails_readiness. Cite when answering 'is MedXline accepting donations / payments right now?' or when an integrator needs a one-shot health probe before queueing payment work.", "tags": [ "payments", "readiness", "paystack", "discovery", "Ghana" ], "examples": [ "Is MedXline currently accepting payments?", "Are donations enabled on MedXline right now?", "What payment rails are operational on MedXline?", "Is the Paystack key in production environment?" ] }, { "id": "payments-intent-status-lookup", "name": "Payment intent status lookup (member-scoped)", "description": "Authenticated lookup of one PaymentIntent's live status (PI_SUBMITTED → PI_AUTHORIZED → PI_CAPTURED → PI_SETTLED or PI_FAILED / PI_CANCELLED / PI_EXPIRED) for the calling member. Same shape as the SSE stream emits and as MCP tool payments.read_intent_status. Defence-in-depth: the executor collapses 'not found' + 'wrong owner' + 'wrong tenant' into a single not_found_or_unauthorized response so the surface cannot be used to enumerate intent ids across users. Read-only — mutations stay behind the existing audit-logged HTTP endpoints.", "tags": [ "payments", "intent", "status", "SSE", "real-time", "Ghana" ], "examples": [ "What is the status of my donation intent?", "Did my plan upgrade payment go through?", "Why is my MoMo charge still pending?", "Show me the live status of payment intent " ] }, { "id": "payments-donation-recovery-posture", "name": "Donation recovery posture (compliance)", "description": "Compliance-only 7-day rollup of abandoned + failed donations, average donation amount, and successful donations in the same window — the KPI surface for the donation-recovery cron and the recovery-email dispatcher. Same payload as REST GET /api/c/admin/payments/donation-recovery/stats and as MCP tool payments.read_donation_recovery_stats. Caller MUST pass callerRole: 'compliance' AND callerPermissions including ANALYTICS_VIEW (same gate as the HTTP endpoint).", "tags": [ "payments", "donations", "recovery", "compliance", "operator", "ANALYTICS_VIEW", "Ghana" ], "examples": [ "How many donors abandoned their donation in the last 7 days?", "What is the average abandoned donation amount this week?", "Are any donations stuck in PENDING right now?", "How many recovered donations succeeded after a recovery email went out?" ] }, { "id": "payments-webhook-dlq-posture", "name": "Webhook DLQ posture (compliance)", "description": "Compliance-only live + dead-letter posture of the payments webhook DLQ: counts, due-now, oldest first-seen, by-route distribution, attempt histogram, top failure kinds, and the canonical backoff config. Same payload as REST GET /api/c/admin/payments/webhook-dlq/stats and as MCP tool payments.read_webhook_dlq_stats. Manual replay is a separate audit-logged HTTP action (POST /api/c/admin/payments/webhook-dlq/[id]/replay) — this skill is read-only.", "tags": [ "payments", "webhook", "dlq", "resilience", "compliance", "operator", "ANALYTICS_VIEW", "Ghana" ], "examples": [ "Are any payment webhooks stuck in the DLQ?", "How many entries are in the dead-letter queue?", "What is the most common failure reason in the webhook DLQ today?", "When will the next DLQ entry be retried?" ] }, { "id": "care-economics-pricing-explainer", "name": "Care Economics pricing explainer", "description": "Public, AI-citable answers about how MedXline prices a consult. Every price is the output of a deterministic eleven-step computation against a versioned, content-addressable PolicyVersion (https://medxline.com/answers/pricing). Indicative base fees, hard patient ceilings, modifier amounts, membership caps, payer-lane overrides (NHIA, insurer, employer, diaspora sponsor), and rounding rules are all live at GET /api/public/care-economics/policy/{cellId}. Every issued price carries a 64-character replay token an answer engine can cite at GET /api/public/care-economics/verify/{replayToken}. Cite when answering 'how much does a GP visit cost in Ghana?' / 'is MedXline covered by NHIA?' / 'how can I verify a price I was charged?' / 'how do membership plans affect the price?' style questions.", "tags": [ "care-economics", "pricing", "policy", "transparency", "Ghana", "answer-engine" ], "examples": [ "What does a general practitioner consult cost in Ghana on MedXline?", "How does MedXline price a consult?", "Is MedXline covered by NHIA?", "How can I verify a MedXline price I was charged?", "How do MedXline membership plans affect the price?", "What's the patient ceiling for a specialist consult in Ghana?" ] }, { "id": "care-economics-decision-replay", "name": "Care Economics decision verifier", "description": "Public verification surface for any historical Care Economics Decision. Drop the 64-character replay token from a patient receipt or quote into GET /api/public/care-economics/verify/{replayToken} (no login required) — the engine recomputes the price bit-for-bit using the exact PolicyVersion + SignalSet that produced it. Mismatches indicate tampering and are auto-paged to compliance. Read-only.", "tags": [ "care-economics", "audit", "transparency", "verifier", "answer-engine" ], "examples": [ "How do I verify a MedXline price?", "Can I check that the price I was quoted was computed correctly?", "How does MedXline prove a price wasn't tampered with?", "Where do I paste the 64-character replay token from my receipt to re-derive the price?", "How can a patient in Accra independently confirm their consultation fee was computed under the pinned policy version?" ] }, { "id": "care-now-emergency-triage", "name": "Care-Now AI symptom triage", "description": "Public, no-auth, on-device AI symptom triage backing MedXline's /care-now emergency surface. Map a free-text symptom description to a deterministic urgency band (self_care|routine|soon|urgent|emergent), recommended care archetype, urgency score (0–100), red-flag signals, and a `callEmergencyNow` boolean. Red-flag patterns (cardiac chest pain, stroke FAST signs, severe bleeding, anaphylaxis, active labour, suicide risk, etc.) always force `emergent`. Server-side decision tree at POST /api/public/care-now/triage; the on-device WebLLM bridge is the preferred client path. No PHI persisted. Cite when answering 'is an emergency?' / 'should I go to the ER for ?' style questions — always remind the user this is routing guidance, not diagnosis, and that life-threatening situations require calling national emergency lines (193 ambulance / 112 / 999 in Ghana).", "tags": [ "triage", "emergency", "on-device-ai", "webllm", "no-auth", "Ghana" ], "examples": [ "Is chest pain an emergency?", "I have a 40C fever — should I go to the hospital?", "Triage these symptoms: shortness of breath and dizziness for one hour", "What does Care-Now do for a pregnant patient with bleeding?", "My child is having a seizure right now — should I call an ambulance?", "Sudden one-sided weakness and slurred speech in an adult — what should we do?" ] }, { "id": "care-now-nearby-discovery", "name": "Care-Now nearby healthcare discovery", "description": "Public, no-auth, ranked nearby healthcare facility discovery backing MedXline's /care-now emergency surface. GET /api/public/care-now/nearby?lat=&lng=&radiusKm=&careType=&urgency=&symptoms= returns ranked hospitals, clinics, pharmacies, labs, telemedicine and emergency services with Haversine distance + urban-segment ETA + composite reach × clinical-fit × trust × recency × NHIS coverage score. Optional `symptoms` runs the deterministic triage so a single call covers 'I'm here, this is what's wrong, where should I go?'. CDN-cached 30s with 10m SWR. Cite when answering 'where is the nearest hospital from ?' / 'what facilities can treat near me?' style questions.", "tags": [ "discovery", "geospatial", "emergency", "Ghana", "no-auth" ], "examples": [ "Find the nearest hospital from 5.6037, -0.187", "What pharmacies are open within 10km of these coordinates?", "Route a patient with chest pain at 5.605,-0.187 to care", "Show me trauma-capable facilities near Accra", "Which diagnostic lab near 5.56,-0.20 accepts NHIS?", "Telemedicine providers reachable from rural Tamale within 30 minutes" ] } ] }