Skip to content

FFT-TISS-XML - TISS Exchange Format

FFT-TISS-XML is part of the recebimento-medico pack. It is not in the base roster. Install the pack when you need it:

flowforge agents install recebimento-medico

This installs the whole pack: fft-tiss-xml and its peer fft-faturista. The pack is carried inside the FlowForge binary, so installing it downloads nothing. To remove it:

flowforge agents remove recebimento-medico

Both commands are safe to repeat. flowforge agents list shows whether the pack is installed on your machine.

FFT-TISS-XML owns the Padrão TISS exchange format: the XML that carries a guia or a lote from a provider to an operadora. A lote that fails schema validation never reaches analysis, so the lost revenue never shows up as a glosa on the demonstrativo. This agent finds the failing element, names the fix and gets the lote accepted.

It never asserts a TISS version from memory. It looks up the vigente set when you ask. Before it validates anything, it asks which version your operadora accepts. The honest answer to “which version should I send?” starts with a question. Every normative claim carries its source. Anything it cannot source is labelled não verificado.

  • The five components: Organizacional, Conteúdo e Estrutura, TUSS, Segurança e Privacidade and Comunicação. Each one is versioned separately, so there is no single “TISS version” number to quote
  • Two cadences: it tracks the Comunicação schema releases separately from the dated table refreshes between them, which change no schema
  • XSD validation: validation error classes, the mensagemTISS envelope, guia XML structures, lote structure, and encoding, namespace and hash mechanics
  • Version migration: the deltas between Comunicação releases, worked through inside the regulated implantação window
  • Integration debugging: portal upload versus WebService, and an integration that works with one operadora and fails with another
  • Malformed-XML forensics: recovering and diagnosing a file that no longer validates
  • Routing rule: file, schema and wire (XSD, versions, validation, malformed XML, integration) → fft-tiss-xml. Money, process and judgment (glosa, recurso, prazo, pricing) → fft-faturista. Brazilian-healthcare breadth (clinical terminology, LGPD, compliance) → fft-medical
  • A portal or WebService rejected a lote with a schema error
  • A Comunicação version change is coming and your product has to follow it
  • You are building an XSD pre-validation step so schema failures stop at upload

This agent is the other half of the faturista’s work. Under RN 503 (art. 5º, parágrafo único), the right to contest a glosa depends on sending faturamento in the vigente Padrão TISS. This agent keeps you vigente. fft-faturista uses the rights that gives you.

Do NOT dispatch it to judge whether a recurso is worth filing, which prazo applies or how to price. Send those to fft-faturista. General XML or XSD work outside TISS goes to fft-backend. Clinical and LGPD scope goes to fft-medical.

"O portal da operadora rejeitou nosso lote por erro de schema. Aqui estão o XML e a mensagem de retorno: qual elemento falhou e como corrigir?"
"We have to move our TISS output to the next Comunicação release. First ask us what you need to know about which version each operadora accepts, then list the changes."
"Our WebService integration works with one operadora and returns HTTP 500 from another. Here are both request logs. Find the difference."