Solutions Nubiss TelMed

Nubiss TelMed — Telekonsil

Ask a colleague. Keep the whole exchange on the record.

Hausärzte and Fachärzte send a structured, patient-specific question, assess it konsiliarisch, and keep request and answer linked in one traceable record.

Germany only Available for the German market at this stage.

Telekonsil · Hausarzt → Facharzt Synthetic example
Fach Dermatologie routing
Fragestellung Beurteilung einer unklaren Hautläsion, Verlauf 6 Wochen required
Verdacht ICD-10 D48.5 suspected
Frist 3 Werktage · Dringlichkeit routine requested
Anlagen 2 Bilder · 1 Befund (PDF) attached
Antwort Facharztbericht · ICD bestätigt D22.5 returned

Request and response stay linked, and both are rendered into a document for the patient file.

One Telekonsil, request through response. Illustration of the data model with synthetic values.

The old way

Specialist input still travels by phone, fax and post.

The question gets asked — but the context scatters, and nothing links the answer back to it.

Illustration: a general practitioner on the phone beside a fax machine, taking notes by hand
01 Specialist input by phone and fax.

The question gets asked, but the context stays with whoever happened to be holding the notes.

Illustration: two doctors puzzling over posted papers and images with the clinical context missing
02 Findings in the post, context lost.

Findings arrive days later, detached from the question that prompted them.

Illustration: a doctor manually shuffling files between printer, mail and folders
03 Nothing links the question to the answer.

Request and response live in separate files, so neither side has the whole exchange.

With Nubiss

The same question, on the record.

The same conversation between two doctors, kept as one traceable record.

Illustration: a doctor composing a structured consultation request in defined fields
04 The question goes out structured.

A defined clinical question, suspected diagnosis, medication and the documents needed to answer it.

Illustration: two doctors at their own desks, linked by one confirmed consultation record
05 Request and answer linked by one record.

Question, Rückfrage and assessment stay attached to one case rather than scattering across inboxes.

Illustration: the specialist assessment returned with imaging reviewed and the case documented
06 The assessment comes back, documented.

Both practices receive a generated document for the patient file, with the diagnosis code confirmed.

Definition

What a Telekonsil is — and what it is not.

What it is

  • A consultation between two doctors about a specific patient
  • Asynchronous: submitted, assessed, answered in writing
  • Structured: a defined clinical question, suspected diagnosis, medication, a requested response period
  • Documented: request and response linked, with a generated document for each side's patient file

What it is not

  • Not a Videosprechstunde. There is no patient-facing video consultation. The patient is the subject of the question, not a participant.
  • Not a referral. The patient does not travel; the question does.
  • Not a messaging app. No free-text chat — the exchange follows a defined structure so it can be documented and billed.

Two workflows

Both directions are supported.

Any doctor can be the einholender Arzt, and any specialist the Konsiliararzt.

Hausarzt → Facharzt

Specialist assessment before deciding on management — with specialists filtered by specialty, insurance type, languages, city and distance.

Facharzt → Facharzt

A second opinion or another specialty. A case can be forwarded onward with its patient data, slip, diagnosis codes and documents intact.

Requesting doctor

Einholender Arzt

  1. Start from the Überweisungsschein

    Scan the slip's barcode or enter details manually — duplicates are detected.

  2. Choose the specialty and the specialist

    Filter by specialty, insurance, languages, city and distance. You cannot send a consult to yourself.

  3. State the question

    Required Fragestellung, medication, suspected ICD-10 code, urgency, requested response date.

  4. Attach what is needed

    Reports and images up to 50 MB each; metadata stripped; a body map for marking a region.

  5. Answer any Rückfrage

    Flagged cases sort to the top; your answer generates its own addendum document.

  6. Receive and file the assessment

    The written assessment lands on the same case, with a document for the patient file.

Consulting specialist

Konsiliararzt

  1. See what has arrived

    One incoming list, scoped to your practice, urgent cases on top.

  2. Review the case on one page

    Consent, question, body map, slip, reports, and the requesting doctor's LANR and BSNR.

  3. Ask for more if you need it

    Raise a Konsilrückfrage with a deadline; the requesting practice is notified.

  4. Confirm or correct the diagnosis code

    The suspected and the confirmed ICD-10 codes are both preserved — neither overwrites the other.

  5. Return your assessment

    Structured review answers plus your report, rendered into a Facharztbericht with attachments appended.

  6. Close out the documentation

    Confirm insurance status and a valid referral, then complete the case.

One limit worth knowing: there is no explicit decline action. A specialist who cannot assess a case can raise a Rückfrage or close it, but there is no reject-with-reason step that reassigns the consult.

Documentation and transmission

How the record is produced and where it travels.

Generated documents

Überweisungsschein, Facharztbericht and an addendum for supplementary information — attached PDFs appended, drafts stamped as drafts.

Patient consent

Consent under § 367 SGB V — printable, signed on paper and uploaded, stored with a document hash, reusable for up to twelve months.

Transmission

Both practices work inside the platform. Where a practice sends the document by KIM, Nubiss produces the PDF and the practice sends it. Nubiss does not operate a KIM connection itself.

The record also leaves in a standard format

Nubiss TelMed exposes a FHIR R4 interface, so a case record can be read by — and written from — the systems your practice already runs, rather than living only inside Nubiss.

  • Patient, Encounter and DocumentReference as FHIR resources, with search, and a CapabilityStatement that describes exactly what the interface supports.
  • German profiles. Codes are restricted to SNOMED CT, LOINC, ICD-10 and the BfArM ICD-10-GM and OPS systems. A coding outside that set is rejected rather than stored.
  • Both directions. Patients, encounters, reports and observations can be imported from an external system, and changes made in TelMed are sent back to it.
  • Every exchange is logged. Direction, resource, status and a content hash are recorded, so a failed or duplicated transfer is visible rather than silent.

The scope, plainly: the endpoints are authenticated and cover the resource types listed above. This is an integration interface, not a general-purpose FHIR server, and it does not replace KIM or the Telematikinfrastruktur. Nubiss Clinical has a FHIR interface of its own, described on its own page; StudyCore and Longevity have none.

Technical prerequisites, stated accurately

  • There is no KIM client, no Konnektor and no Telematikinfrastruktur integration inside Nubiss TelMed. Where KIM is used, it is your practice's own mailbox.
  • There is no qualified electronic signature, and no eHBA or SMC-B card handling.
  • Attachments accept DICOM files, but there is no image viewer and no PACS or DICOMweb integration — imaging is viewed in your own systems or an external portal.
  • The requested response date is captured and displayed but not enforced — no automatic reminder or escalation.

If your KV or practice requires a specific transmission route or signature method, confirm it against this list before you commit.

Abrechnung

Billing pathways, kept separate.

The general Telekonsil pathway and the radiological pathway are different things with different requirements — and only the first corresponds to a workflow Nubiss TelMed supports today.

General Telekonsil — the supported workflow

EBM positions referenced in the documents Nubiss TelMed generates.
Role GOP Description
Einholender Arzt 01670 Einholung eines Telekonsils
Konsiliararzt 01671 Telekonsiliarische Beurteilung
Konsiliararzt 01672 Additional completed consultation time

What Nubiss does and does not do here

Nubiss TelMed supports the documentation for these positions: the generated documents carry the EBM reference, and the specialist's review records the two prerequisites of insurance status and a valid referral. Nubiss does not bill. There is no billing engine, no GOP field on the case and no KV data export — the claim is made in your practice management system and settled through your KV as usual.

Values, conditions and limits are not reproduced on this page because they change. Check the current EBM for the figures.

Abrechnungsmöglichkeiten und Voraussetzungen können sich ändern und regional unterschiedlich umgesetzt werden. Bitte bestätigen Sie die konkrete Abrechnungsfähigkeit vor Nutzung mit Ihrer zuständigen Kassenärztlichen Vereinigung.

Billing options and prerequisites can change and are implemented differently from region to region. Please confirm eligibility with your regional Kassenärztliche Vereinigung before use. Nubiss does not guarantee that any consultation is reimbursable.

Radiological Telekonsil — not available today

Nubiss TelMed does not currently provide a radiological teleconsultation workflow. There is no image viewer, no PACS or DICOMweb integration, and none of the positions below are referenced anywhere in the product. They are listed so the distinction from the general pathway is explicit, and because this is a direction we are considering — not because it is available.

EBM positions for the radiological pathway. Listed for completeness only.
Workflow GOP
Request for radiological consultation 34800
Assessment of radiographic images 34810
Assessment of specified CT examinations 34820
Assessment of specified CT examinations 34821

Abrechnungsmöglichkeiten und Voraussetzungen können sich ändern und regional unterschiedlich umgesetzt werden. Bitte bestätigen Sie die konkrete Abrechnungsfähigkeit vor Nutzung mit Ihrer zuständigen Kassenärztlichen Vereinigung.

In the practice

Built around how a practice actually runs.

  • Staff prepare a case as a draft; a doctor claims and sends it
  • German patient dataset: KVNR, Kostenträger, Institutionskennzeichen, Versichertenstatus
  • Status-change notifications that carry no patient details
  • Two-factor authentication with printable backup codes
  • Lockout after repeated failed sign-in attempts
  • Access limited to the case's creator, sender and assigned specialist

Security posture

Encrypted in transit with strict transport security, a strict content security policy and short sessions. Files stored with server-side encryption. Every change goes to a tamper-evident, append-only log on a separate database, with no patient data in the log entries.

There is no end-to-end encryption and no field-level database encryption — the security page sets out the full position.

Questions

Common questions

Every answer here is the honest one — including the things the product does not do yet.

Is this a video consultation product?

No. Nubiss TelMed is asynchronous and written. There is no patient video consultation, and the doctor-to-doctor video feature in the codebase is switched off and not offered.

Do we need KIM or a Konnektor to use it?

Not to use the platform — both practices work on the case inside Nubiss TelMed. If your workflow requires the document to travel by KIM, you send the generated PDF from your own KIM mailbox.

Can we bill through Nubiss?

No. Nubiss supports the documentation; the claim is made in your practice management system and settled through your KV. Confirm eligibility with your KV before you rely on it.

Can Nubiss TelMed exchange data with our existing systems?

Yes, over FHIR R4. Patients, encounters and reports can be imported from your system and are sent back as they change, using the German FHIR profiles and the BfArM code systems. It covers those resource types rather than everything in your record, and it is separate from KIM — that route is unchanged.

Can we send imaging?

You can attach DICOM files, images and PDFs up to 50 MB each, or link to an external image portal. There is no viewer inside Nubiss — images are read in your own systems.

Which specialties are available?

Specialty-specific question sets cover dermatology, rheumatology, cardiology and paediatric ophthalmology; the general question set applies everywhere, and new specialties are configured on request.

Is the interface in German?

The application ships German translations and the clinical forms are written in German. This marketing page is in English while the German version is prepared.

For requesting practices

See how a Telekonsil is raised, what the specialist receives, and what lands back in your patient file. Please do not include any patient information in your message.

For specialists

If you take consults in your specialty and want to receive them with the information needed to answer properly, we would like to talk. Please do not include any patient information.