canonical: https://jentic.com/apis/qs-mdx.mdportal.de/qs-mdx-mdportal # Qs Mdx Mdportal De MD-X Portal - API Dokumentation für Krankenkassen The MD-X Portal API connects German statutory health insurers (Krankenkassen) to the MD-X Portal of the Medizinischer Dienst, so their systems can exchange review cases (Vorgänge) and the documents behind them. It searches cases by status, fetches cases ready for processing, acknowledges and sends them, and uploads and downloads eVV documents, including several at once as a ZIP. It also creates, edits, reads, and cancels Erörterungsverfahren requests and returns receipts (Quittierung) and system notices. ## For AI agents Search and fetch MD-X Portal review cases for a German health insurer, acknowledge and send them, upload or download eVV documents, and create or cancel Erörterungsverfahren requests. ## Scope Does not access patient EHRs, submit hospital claims, or process payments. Use for exchanging review cases and eVV documents between German health insurers and the MD-X Portal only. ## Capabilities - Search Vorgänge by typisierung and a status such as SENT, ANSWERED, or REJECTED, with offset and limit paging - Fetch cases ready for processing in a kontext such as EV_DOWNLOAD or EV_ABLEHNUNG and acknowledge each by processId - Upload an eVV document to an existing case with a documentTitle, and download one or several documents as a ZIP - Create an Erörterungsverfahren request with krankenhaus, auftrag, versicherter, and aufenthalt details, then edit or read it - Cancel an Erörterungsverfahren with a stornierungsMeldung and read any rejection (Ablehnung) - Download the latest receipt (Quittierung) for a case and read the eVV document classification - Read portal system notices by kategorie and relevantFrom, plus health and version checks ## Use cases ### Agent-run case inbox through Jentic A claims-operations agent at a health insurer works the MD-X inbox: it fetches cases ready for download, acknowledges each by processId, and downloads the documents for the case worker. Through Jentic the portal JWT is injected by the developer's own Jentic One instance, and rules keep the agent to read and acknowledge operations. Example prompt: GET `/v1/vorgang/todo` with kontext 'EV_DOWNLOAD', then for each case POST `/v1/vorgang/acknowledge` with its processId and GET `/v1/evv/dokumente/zip` with the dokumentenIds ### Erörterungsverfahren requests When an insurer and hospital dispute a billing review, the insurer opens an Erörterungsverfahren. POST `/v1/ev/anforderung` requires krankenhaus, auftrag, versicherter, and aufenthalt, PATCH edits it by vorgang, and POST `/v1/ev/stornierung` cancels it with a stornierungsMeldung. Example prompt: POST `/v1/ev/anforderung` with the krankenhaus, auftrag, versicherter, and aufenthalt objects for the stay, then POST `/v1/vorgang/send` with the returned processId ### eVV document exchange Cases carry documents under the eVV agreement. POST `/v1/evv/dokument` uploads a file to an existing case with a required documentTitle and optional beschreibung, GET `/v1/evv/klassifikation` returns the document classification, and GET `/v1/evv/dokument` downloads a single document by dokumentId. Example prompt: POST `/v1/evv/dokument` with processId '4711', documentTitle 'Entlassbrief', and the PDF as dokument ### Case status monitoring GET `/v1/vorgang/search` filters cases by status, such as PROCESSING, ANSWERED, REJECTED, or FINISHED, so an agent can report which reviews moved and pull the latest Quittierung for each with GET `/v1/quittierung.` Example prompt: GET `/v1/vorgang/search` with status 'ANSWERED' and limit 50, then GET `/v1/quittierung` for each processId ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/v1/vorgang/todo` | Cases ready for processing | | GET | `/v1/vorgang/search` | Search cases | | POST | `/v1/vorgang/acknowledge` | Acknowledge a case | | POST | `/v1/vorgang/send` | Send a case | | POST | `/v1/evv/dokument` | Upload an eVV document | | GET | `/v1/evv/dokumente/zip` | Download several documents | | POST | `/v1/ev/anforderung` | Create an Erörterungsverfahren | ## Key resources - **Vorgang (cases)** — Search, to-do list, acknowledge, send, and delete review cases - **eVV documents** — Upload, download, delete, ZIP download, and document classification - **Erörterungsverfahren** — Create, edit, read, cancel, and read rejections - **Quittierung** — Latest receipt for a case - **System** — Health, version, tenant data, and system notices ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 51 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 99 / 100 - Developer Experience & Jentic Compatibility: 77 / 100 - AI-Readiness & Agent Experience: 23 / 100 - Agent Usability: 94 / 100 - Security: 75 / 100 - AI Discoverability: 55 / 100 - **View full report:** https://jentic.com/apis/qs-mdx.mdportal.de/qs-mdx-mdportal/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the MD-X Portal by hand means obtaining a JWT bearer token, choosing between its two portal hosts, and threading processId through query parameters and multipart uploads yourself. Through Jentic you install once, import the MD-X Portal API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The MD-X Portal passes processId as a query parameter rather than a path segment, so rules bound which operations your agent may call, not which case. You choose the operations it may call, so destructive ones like case deletion or document deletion are not included unless you add them. - **Credential handling:** Your MD-X Portal token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'fetch cases ready for download' or 'upload an eVV document', and Jentic returns the matching MD-X Portal operation with its input schema so the agent calls the right endpoint without reading the German reference docs. ## Related APIs - **Epic FHIR API** — Hospital-side clinical records over FHIR - **PDF.co API** — PDF conversion, merging, and extraction ## FAQ ### What authentication does the MD-X Portal API use? The MD-X Portal API declares an HTTP bearer scheme (bearerAuth) with a JWT format in its OpenAPI spec, applied globally. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context. ### Which servers does the MD-X Portal API use? The spec lists two hosts: https://qs-mdx.mdportal.de/api/kk, whose qs- prefix marks it as the quality-assurance (test) host, and https://mdx.mdportal.de/api/kk. Point test integrations at the qs- host before switching to the other. ### What are the rate limits for the MD-X Portal API? The OpenAPI spec does not specify rate limits. List operations page with offset and limit, each capped at 100 in the spec. For current limits, ask the Medizinischer Dienst via the portal at https://mdx.mdportal.de. ### How do I fetch cases ready for processing through Jentic? Install Jentic One, import the MD-X Portal API from the Jentic API Directory, and store your portal token. Your agent searches for 'fetch MD-X cases ready for processing', Jentic returns GET `/v1/vorgang/todo` with its schema, and the agent calls it with a kontext such as EV_DOWNLOAD. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there an MD-X Portal MCP server? You don't need an MCP server to give your agent the MD-X Portal API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, discovering operations on demand rather than loading every tool definition into its context. ### Can I limit what my agent is allowed to do with the MD-X Portal API? Yes. Write a rule that allows only GET `/v1/vorgang/todo`, POST `/v1/vorgang/acknowledge`, and GET `/v1/evv/dokumente/zip`, so the agent can work the download inbox while sending cases, deleting documents, or cancelling an Erörterungsverfahren stays out of reach. Every call it makes is logged.