Care Orchestration Platform
Identity, verified provider supply, availability, booking, consent, logistics, payment and support.
Für MVP, Sicherheit, Datenschutz und Pilotvorbereitung. Einmaliger Support ohne Beteiligung oder Rendite.
JT Health AI · Care Platform · interactive concept
A care-orchestration concept for appointments, coordination and payment, connected to Clinical Reasoning AI in development. Clinics and reliable care operations come first. Synthetic demo only: no real booking, no approved medical device, no patient data.
Verified appointment options or a navigator response within 24 hours
Not an emergency service. No guarantee of outcome, diagnosis or a specific specialist.Identity, verified provider supply, availability, booking, consent, logistics, payment and support.
Patient-specific clinical information, safety signals, hypotheses and evidence-linked options for professional review.
The booking layer does not diagnose or interpret symptoms. Emergency concerns stop the routine flow and direct the person to local emergency services or human clinical review.
Availability, credentials, language and format are checked without using a provisional diagnosis for commercial ranking.
Open integration concept · Planned capabilities
JT Health is being designed to connect health professionals, service providers and patients. Practices should be able to choose reviewed partner integrations or connect their own systems through a documented API.
Planned adapters connect telephone assistants, practice calendars and transport services. Each provider receives only the information needed for its task, with a clear handover to a person when required.
Providers may be recommended after review. Names shown in this prototype are examples; they do not establish a partnership or a live connection.
A planned developer portal will provide API documentation, versioned interfaces, example integrations and a test environment. Practices and their developers will be able to register their own integrations and request specific permissions.
Access is intended to be limited to the authorised organisation, purpose and data. A documented API does not mean public access to patient records.
A planned patient area will let people upload their own reports, complete intake information and choose which treating professionals can access it. Patients should be able to review and withdraw future sharing permissions.
AI-assisted summaries are planned as traceable drafts for review. Uploading a document will not automatically create a diagnosis, treatment recommendation or consent to train an AI model.
These capabilities are not live. This public prototype accepts no patient uploads or production credentials. Initial demonstrations use synthetic data. API access, partner connections and patient uploads require implementation and technical, privacy and clinical review before activation.
Integration foundation
The planned interface foundation uses REST APIs and webhooks; clinical data exchange will evaluate HL7 FHIR and SMART on FHIR where supported by the source system. Every connector receives only the minimum data required for its job. Clinical reasoning stays versioned and separately governed.
Consent, callback request and transcript metadata; no clinical conclusion.
Examples: Fonio · SIP/VoIP provider · human call centreinbound webhook · consent marker · human handoverFree/busy, appointment type, location and cancellation policy.
Examples: Microsoft 365 · Google Calendar · Cal.comread availability · hold slot · confirm · cancelExplicitly authorised records with provenance; isolated from marketplace ranking.
Examples: FHIR R4 endpoint · EHR export · patient uploadpatient match · consent · provenance · revocationPayment tokens, split instructions, refunds and payouts; no health record on ledger.
Examples: licensed PSP · marketplace payout providermarketplace payout · SCA · refund · reconciliationPickup, accessibility and itinerary data after explicit patient approval.
Examples: mobility API · human travel deskquote · book · change · cancelIntegration Studio · Prototype
Geplant sind geprüfte Partneranbindungen und dokumentierte Schnittstellen für eigene Kundenintegrationen. Diese Ansicht illustriert die Konfiguration; sie aktiviert keine Verbindung. Geheimnisse, Gesundheitsdaten und echte Webhooks werden hier nicht gespeichert.
Credentialing, scope of practice, jurisdiction and availability before marketplace growth.
If automation cannot safely or fairly complete the journey, a person takes over.
Use a licensed marketplace payment provider. A public blockchain is not the default and never stores health data.
Commercial incentives must never influence clinical reasoning, urgency or professional review.
JT HEALTH AI · PILOT IN VORBEREITUNG
Wir bereiten 10 kostenlose Pilotplätze für qualifizierte Gesundheitsfachpersonen und klinische Teams vor. Eine Vormerkung ist noch keine Freischaltung oder Zusage.
Ausgewählt wird nach Berufsqualifikation, passendem Test-Anwendungsfall und Bereitschaft zu Feedback. Keine zufällige Verlosung. Die kostenlosen 90 Tage beginnen erst mit individueller Aktivierung, sobald Testreife und erforderliche Freigaben vorliegen.
Der Pilot umfasst eine Einführung und strukturiertes Feedback zu Bedienbarkeit, unklaren Ausgaben und Fehlern. Termine, Zeitaufwand und Feedbackformat werden vor Aktivierung schriftlich vereinbart. Bis zur klinischen und rechtlichen Eignung sind ausschließlich synthetische Testfälle erlaubt. Keine Patientenversorgung und keine echten Gesundheitsdaten.
Der Pilotzugang endet nach 90 Tagen ohne automatisches kostenpflichtiges Abo. Ein regulärer kostenloser 30-Tage-Test ist erst mit einer stabilen Testversion vorgesehen und noch nicht verfügbar. Spätere Produktpreise sind offen. Instagram-Teilen und finanzieller Support sind freiwillig und beeinflussen die Auswahl nicht.
Für die erste E-Mail reichen Berufsrolle und Testinteresse. Bitte keine Patient:innenunterlagen oder Gesundheitsdaten senden. info@jt-health.at