When PIAS Goes Down: What Patients Can Request and Who Is Responsible for Continuity of Care

When PIAS Goes Down: What Patients Can Request and Who Is Responsible for Continuity of Care

Rating
—/5 0 ratings
Follow us on Google News
News10 min read

An error involving the health insurance card or an electronic prescription does not automatically mean that a patient must leave without a consultation, medication or diagnostic test. The current framework allows services to be provided offline when an interruption to a component of the Health Insurance IT Platform (PIAS) has been identified and communicated by the National Health Insurance House (CNAS).

For more information on the health insurance card, see also The electronic ID card does not yet replace the health insurance card: what CNAS’s September 3 update means, which provides complementary details on the subject.

The distinction matters. The phrase “the system is not working” can refer to a central outage, but also to an internet, software application, digital certificate, card reader or provider-configuration problem. For the patient, the immediate consequence is the same: a service may be delayed. The responsibilities and administrative solutions, however, are not identical.

What the public documents show: CNAS issued procedures for activities provided offline in February 2025, for malfunctions in December 2025, and for periods in January–February 2026. The repeated procedures show that the continuity mechanism is not merely theoretical. However, the documents reviewed do not make it possible to establish a complete archive of incidents, their technical causes, the duration of each outage or the number of patients affected.

When PIAS is not working, the rule begins with a CNAS notification

The rules in the Framework Contract, in the version published by CNAS, make offline activity conditional on CNAS identifying and communicating an interruption to a PIAS component. The regulation also provides for an order to be issued for the days on which the system was unavailable, as well as rules for subsequently submitting data to the insurance house.

In other words, a medical practice, pharmacy or laboratory must be able to follow a later reporting and validation procedure. This is the provider’s administrative safeguard: a service provided during a recognised outage window can subsequently be entered and checked, under the conditions set by CNAS.

The rule does not, however, amount to a simple requirement that every error seen at a counter automatically obliges a provider to follow the same process. If CNAS has not issued a notification of a central outage, it must be determined whether the problem lies with local infrastructure or the application used by the provider. Patients should not be turned into technical arbiters, but this distinction explains why responses may differ from one place to another.

PIAS is not a single screen. CNAS technical documentation describes separate components and workflows, including the Integrated Single IT System (SIUI), the Electronic Prescription IT System (SIPE) and the electronic health insurance card infrastructure (CEAS). A problem with electronic prescriptions does not in itself prove that all services on the platform are unavailable.

What can continue offline — and what this mechanism does not solve

During officially covered periods, the logic of the procedure is that the service is provided, with its record submitted and validated later. For electronic prescriptions, CNAS documentation defines an offline prescription as a form generated without a connection to SIPE and subsequently entered into the system for validation.

CNAS orders published for February 2025, then for the December 2025 malfunctions and for January 2026, set specific rules for submitting and validating activities provided offline. They confirm that there were periods requiring subsequent regularisation. They are not, however, technical logs and do not on their own explain the cause of each malfunction.

Observed problem What it may mean What is useful for the patient
The card cannot be read It may be a problem with the card, reader, connection or a central PIAS component. Ask for the specific reason given by the provider and, if the service is not provided, evidence of the refusal or rescheduling.
An electronic prescription cannot be issued or processed The SIPE workflow or the local application may be affected. Ask whether the offline prescription process applies, and keep the document received.
A consultation or test is postponed There may be an official outage, but also a local operational decision. Request the date, time, reason and new appointment in writing or in a verifiable message.
Full payment is requested The specific basis needs to be clarified: uninsured status, a service not covered by contract, a local error or PIAS unavailability. Ask for an explanation and a fiscal receipt or invoice; payment should not automatically be presented as the unavoidable consequence of a technical error.

The offline regime can protect continuity of medical care and the provider’s subsequent reimbursement. It does not automatically remedy a missed consultation, an unnecessary journey, a rescheduled appointment or the cost of a private alternative. Nor do the public documents reviewed describe a single, detailed and separate route for a patient who says a service was refused during an official outage.

The chain of responsibility: from alert to reimbursement

The issue becomes clearer when treated as a chain rather than a general dispute about “the system”.

  1. CNAS identifies and communicates the unavailability of a PIAS component and sets out, through procedures or orders, how the activity is to be regularised.
  2. The medical provider or pharmacy applies the available workflow for the type of service, retains the necessary data and reports it later under the set conditions.
  3. The health insurance house subsequently validates services reported under the procedure applicable to the relevant period.
  4. The patient, if a service is refused, needs an explanation that can be checked: what service was requested, when, from which provider, and the reason given.

The provider’s financial risk is linked to the ability to report and obtain subsequent validation. The patient faces a different risk: losing timely access to care or incurring a cost that has not been clearly explained. The two problems may overlap, but they should not be confused.

A position issued in 2025 by the National Federation of Family Doctors’ Employers’ Associations called for clarification of offline procedures and argued that services provided when PIAS is not working should not be charged back to doctors. This is the providers’ perspective, relevant to their administrative risk; it is not a national statistic on the number of patients affected.

Documents worth requesting if a service is refused or postponed

A patient does not have to prove the technical cause of a failure. But they can document the specific effect on their case. A complaint based only on the statement that “the card was not working” is difficult to verify later; one that records the service, the time and the provider’s response can be assessed.

  • proof of the appointment, referral slip or medical recommendation, where applicable;
  • the date and time of attendance, and the provider’s name and address;
  • a message, note, proof of rescheduling or written explanation of the reason for refusal;
  • the receipt, cash-register receipt or invoice, if payment was made for a service that the patient believes should have been clarified through the insurance arrangement;
  • the prescription, result, referral or other medical documents already issued, without publishing personal data or diagnoses online.

A reasonable first step is to request an explanation from the provider that refused, postponed or charged for the service. If the response does not clarify the case, the documents can support a complaint to the health insurance house with which the provider has a contract. It is useful for the complaint to request a specific answer: whether an official PIAS outage had been announced for the stated period, which offline rule applied to that type of service, and whether the provider’s decision was compatible with that procedure.

Nothing in the documents reviewed for this article provides a basis for automatically promising reimbursement of a payment or compensation. That depends on the type of service, insurance status, the provider’s contract, the documents available and the response of the competent institutions.

Why not all outages can be treated the same way

CNAS has also announced scheduled unavailability for operational deployment. A pre-announced shutdown has a different status from an unplanned incident: it may allow providers to prepare and apply offline workflows during the stated window, but it does not by itself prove a system failure.

Conversely, an error message at a medical practice does not demonstrate a nationwide outage. A serious assessment of each episode would require its start and resolution times, the affected component, the CNAS notification, the applicable order, the documented technical cause and the outcome of subsequent validations. A single, complete public archive containing these elements was not identified in the documents analysed.

The Court of Accounts audit of PIAS implementation, operation and administration is an important reference precisely because it examines the infrastructure beyond an isolated episode. The institution said its assessment included interviews, visits and 1,039 questionnaires sent to providers, and recommended in its statement that malfunctions affecting providers and service beneficiaries be remedied. The Court also indicated the system’s scale: more than 18 million potential beneficiaries, more than 70,000 users, and more than 700,000 services reported and validated daily, including approximately 200,000 prescriptions. These figures describe the operational stakes; they do not measure daily technical availability.

PIAS modernisation is not yet evidence of continuity

Law No. 157/2026 introduced a framework for developing new tools in PIAS, including the e-HealthaMea portal and a national appointment-booking portal. Legislative documents set an August 31, 2026 deadline for the Recovery and Resilience Facility project to resize, standardise and optimise PIAS. The 2026–2030 National Health Digitalisation Strategy likewise sets out the objective of a reliable, scalable and efficient platform.

These are legislative and strategic commitments, not evidence that every component has been delivered, tested, accepted and put into operation without problems. The same distinction matters in the broader discussion about digital public services: the existence of a portal or a funded project does not automatically mean that a user can complete every stage without obstacles. An InfoBuz analysis of public services available fully online shows the same gap between digital listing and the effective completion of a procedure.

The verifiable question for PIAS remains one of continuity: which period was affected, which component was unavailable, which procedure was communicated, how many services were subsequently validated, and how many remained unresolved. Without these data, neither contractual responsibility nor the impact on patients can be measured properly.

What should be public so patients can check the situation

The rules allow offline activity, but the transparency a patient needs is simpler than the platform’s technical architecture. For every relevant outage, the following should be available in an accessible place:

  • the affected PIAS component and the precise period of unavailability;
  • the difference between scheduled maintenance and an unplanned incident;
  • the official notification and the applicable order or procedure;
  • the types of services that can be provided offline and the subsequent reporting steps;
  • a clear channel for patients whose service was refused or postponed;
  • aggregated data on regularised services, rejected services and the main reasons for rejection.

This information would reduce conflict between patients and providers: patients would not be left to guess whether a problem was central, and providers would have a visible, verifiable procedure. Until then, the best practical protection for patients is to ask for a precise response and retain documents showing which service was affected and when.

Frequently asked questions

Can a doctor provide a consultation if PIAS is unavailable?

During periods in which an interruption to a PIAS component has been identified and communicated by CNAS, the rules provide for services to be delivered offline and reported later. The practical application depends on the type of service and the procedure in force for the relevant period.

If a pharmacy cannot process an electronic prescription, must I pay the full price for the medicine?

A simple technical error does not establish that full payment is automatically mandatory. Ask for the specific reason, whether an applicable offline workflow exists, and keep the fiscal documents or message received. The situation may depend on the type of prescription, insurance status and the active procedure.

Where can I complain about a medical service refused because of PIAS?

Start with the provider that refused or postponed the service and request a written response. If the situation remains unclear, you can notify the health insurance house with which the provider has a contract, stating the date, time, requested service and available documents.

Sources consulted

Etichete: Health cardNational Health Insurance House (CNAS)Healthcare DigitalizationPatient RightsPIASElectronic PrescriptionMedical services
Share this article
COMUNITATEA INFOBUZ

Discuția cititorilor

Ai o opinie sau o întrebare despre acest articol? Spune-ne ce crezi.

0 comentarii

Fii primul care deschide discuția.

Lasă un comentariu

Email address este vizibilă doar administratorilor și nu va fi publicată. Câmpurile marcate cu * sunt obligatorii.

Te rugăm să păstrezi un limbaj civilizat și să discuți la subiect. Comentariile spam sunt filtrate automat.