Clinical AI infrastructure · by DAS Medhub

Clinical intelligence,
built into your workflow.

Turn supported clinical documents and text into structured, reviewable clinical outputs through APIs. Integrate document intelligence, clinical information extraction and interoperability workflows into the healthcare software you already use.

Request an API Demo Explore the API Workflow
  • API-first architecture
  • Existing-system integration
  • Workflow-specific capabilities
Clinical document example

c/o: vertigo - 3 days. Tinnitus left ear.
TAB BETAHISTINE 16mg p/o twice daily…

POST /api/v1/…
Clinova Clinical AI API
OCRExtractionStructured output
200 · JSON
"entities": [
  { "type": "symptom", "normalized_text": "vertigo" },
  { "type": "medication", "normalized_text": "betahistine" }
]

The problem

Clinical information is everywhere. Usable clinical data is not.

Handwritten notes, scans, PDFs and free text carry the detail of a consultation, yet software can only act on data it can read and structure.

Existing applications often lack the means to extract text, structure findings, summarize encounters, normalize terminology or emit interoperable records. Clinova supplies those as separate API workflows. Your application decides what to show, review, store or act on.

What the API does

Six capability groups, each with its own endpoints.

Workflows are called separately, and outputs are designed for review by qualified staff.

Document intelligence & OCR

Extracts text from scans and PDFs, including multi-document requests. Persisted OCR can be retrieved and a reviewed version submitted back.

Input
Image, PDF (up to 50 pages), TXT
Processing
OCR
Output
Extracted text
POST /api/v1/ocr

Clinical extraction & summarization

Turns text or processed documents into typed entities, summaries and SOAP drafts, and flags documentation gaps. Translation is also available.

Input
Text or document
Processing
Extraction, summary, SOAP, gaps
Output
JSON in result
/entities · /summary · /soap · /gaps

Terminology & coding

Normalizes clinical terms, then looks up SNOMED CT and ICD-11 candidates. Candidates are suggestions for clinician or coder confirmation.

Input
Text or document
Processing
Normalization, code lookup
Output
Per-term candidate lists
/normalization · /snomed · /icd

Structured interoperability

Generates FHIR R4 resources from clinical content and validates them, so your pipeline can receive standards-shaped data.

Input
Text or document
Processing
FHIR R4 generation, validation
Output
Resource wrappers
POST /api/v1/fhir

Master-data matching

Matches OPD entities and pharmacy invoice items against candidate records you supply. Scored matches are returned, and accepted or corrected outcomes can be recorded.

Input
OPD text/documents or invoice items, plus your candidates
Processing
prepare, map, feedback
Output
Scored matches
/api/v1/hims-matching/…

Medication safety

Looks up drug interactions and adverse events and supports PRR/ROR-style safety-signal analysis for your pharmacists and prescribers.

Input
Drug, medication list or document
Processing
Interactions, safety signals
Output
Findings and risk assessment
/api/v1/pharmacovigilance/…

How it works

One integration path, five steps.

  1. 01Your applicationYour HIMS, EMR, clinical app or authorized client starts the workflow.
  2. 02REST API requestIt submits supported input to the appropriate Clinova endpoint.
  3. 03Clinova processingThe relevant documented clinical AI workflow runs.
  4. 04Structured responseClinova returns that endpoint's output as JSON.
  5. 05Your workflow continuesYour application presents it for review or uses it downstream.

Add clinical AI capabilities without replacing your existing healthcare software.

Integration still requires implementation work on your side; scope and effort depend on your systems and chosen workflows.

Demonstration

What a request and response might look like.

See how a request and its structured response look for each workflow. Responses are shortened for readability.

Illustrative API Demonstration

Request

Response (illustrative)

      

    

  






  

    
Use cases
Where integrators can apply it.
Supported workflows, not claims of existing deployments or validated outcomes.

    
    
      
  • Scanned OPD documentationSend a scan to /ocr and show the text to staff for review before it enters the record.
    • 
      
  • Summaries and SOAP draftsReturn structured drafts that clinicians check and edit in your interface.
    • 
      
  • Terminology and code candidatesNormalize terms and retrieve SNOMED CT and ICD-11 candidates for confirmation.
    • 
      
  • FHIR R4 outputProduce validated resource wrappers for your own interoperability pipeline.
    • 
      
  • Master-data matchingLink extracted entities and invoice lines to catalogues your system supplies.
    • 
      
  • Medication safety reviewRun interaction and adverse-event lookups on a medication list or document.
    • 
    

  






  

    
Integration
Keep your systems. Add selected capabilities.

    
Clinova does not implement patient management, scheduling or billing, and has no required user interface. Your organization decides how responses are presented, reviewed, stored and used.

    

      
Hospital application / HIMS / EMR
Clinova REST API
Clinical AI engine
API response
Existing application

    

    
DAS Medhub also uses a static demonstration frontend to show how outputs may look. It is an evaluation aid, not part of the product.

  






  

    
Technical overview
For IT teams and software vendors.

      
    
        
  • REST API with JSON requests and responses, and one endpoint per workflow.
    • 
        
  • A shared request and response envelope across the clinical workflows.
    • 
        
  • Inputs: plain text, images, PDFs and text files, individually or as multi-document requests.
    • 
        
  • Outputs aligned to FHIR R4, SNOMED CT and ICD-11.
    • 
        
  • API reference documentation provided during technical evaluation.
    • 
      

    

  






  

    
Why Clinova
Why teams choose to integrate Clinova.

    
Practical reasons hospitals and healthcare software vendors add Clinova to their existing applications.

    
    
      
  • Keep the systems you haveAdd clinical AI to your existing HIMS, EMR or clinical application. No replacement and no change of platform.
    • 
      
  • Adopt one workflow at a timeEach capability has its own endpoint. Start with document OCR or summaries and add others as your needs grow.
    • 
      
  • Structured, standards-aligned outputJSON responses, FHIR R4 resources, and SNOMED CT and ICD-11 candidates ready for your own pipelines.
    • 
      
  • Designed for clinician reviewOutputs are drafts and candidates. Your application controls how they are presented, reviewed and stored, and reviewed OCR text can be submitted back.
    • 
      
  • Works with the documents you already holdScans, PDFs, images, plain text and multi-document requests.
    • 
      
  • Your master data stays the referenceMatch extracted items against the catalogues and records your organization supplies.
    • 
      
  • Security and deployment scoped to youData handling, access and deployment requirements are worked through with your IT and security teams during technical evaluation.
    • 
    

  






  

    
Next step
Evaluate Clinova against your workflows.

    
    
      
  1. Discuss your clinical documentation or integration requirements.
    2. 
      
  2. Identify the relevant Clinova API workflows.
    3. 
      
  3. Review the documented inputs and outputs.
    4. 
      
  4. Determine technical, deployment and security requirements.
    5. 
      
  5. Agree an appropriate demonstration or pilot.
    6. 
    

  






  

    
FAQ
Common questions.

    
What is Clinova?
An API-only clinical AI inference service from DAS Medhub, built on the Penthus Clinical AI Engine, that processes clinical documents and text through supported workflows.

    
Is Clinova an HIS, HIMS, EMR or EHR?
No. It does not implement patient management, scheduling or billing. It is called by the software you already use.

    
How does it integrate with existing software?
Your application sends HTTP requests to the relevant endpoints and handles the JSON responses. Scope depends on your systems and is assessed during evaluation.

    
Which inputs are supported?
Direct text, images, PDFs (up to 50 pages), plain text files and multi-document requests.

    
Does every capability use the same endpoint?
No. Each workflow has its own endpoint, with a shared request envelope for the clinical workflows.

    
Does it return structured outputs and support FHIR R4?
Yes. Workflows return JSON, and /api/v1/fhir generates and validates FHIR R4 resources.

    
How can we evaluate it?
Request a technical demonstration below, then follow the evaluation steps.

    
What does an evaluation cover?
Your clinical documentation and integration requirements, the relevant workflows and their inputs and outputs, and your security, data-handling and deployment requirements, leading to an agreed demonstration or pilot.

  






  

    
Contact
Bring clinical AI into your existing healthcare workflows.

      
Explore how Clinova's API capabilities can support your organization's clinical documentation, structured data and interoperability requirements.

      
 Do not include patient information in this form.

    

      
      
      
      
      
      
      
      
      
      
Your enquiry is sent to the DAS Medhub team. Please do not include patient information.