The intake form has fourteen fields.
She filled in the eleventh one at 9:47 PM, during dinner, which she did not plan to do. The form was on the table because she had left it there this afternoon — the five remaining fields marked Monday in pencil, the pencil still sitting in the crease of the open folder — and when she sat down with her bowl she picked up the pen without thinking. Field eleven: current primary care provider name and NPI. She wrote Dr. Marchetti's name in her clearest handwriting, then the NPI number, which she had memorized during her first year coordinating UPMC intake, when memorizing NPI numbers and UPIN-chain codes and error-class identifiers was a way of feeling that she knew what she was doing. She wrote it without checking.
Then she put the pen down and ate dinner.
The intake form is for Dr. Marchetti's new practice — she transferred out of the hospital system in January, opened a private clinic in Lawrenceville. September 4, 2:15 PM. Six days. Magda found the appointment card when she was cleaning her bag on Thursday, after UPMC-ERR-2027-B was resolved, and she had not known until that moment that she had been carrying the card for three weeks. She set it on the refrigerator behind the Krakow magnet, then moved it to beside the magnet so it was visible, and stood in the kitchen until she understood that she had been running the appointment management in parallel with the escalation for three weeks without registering that she was managing both at once.
That was Thursday morning. Today is Saturday night.
UPMC-ERR-2027-B was an escalation-class error in the patient record portability system — specifically, a failure in the cross-registry synchronization layer that handles record transfers during care coordinator reassignments. When the escalation was first flagged, in early spring, the system logged it as a tier-2 handoff anomaly. The tier-2 category meant: something is wrong, someone should look at it. Someone looked at it and found that the wrong someone was looking at it and escalated to tier-3. Tier-3 meant: Magda.
She is not going to think about it again tonight. She knows this because she has been not thinking about it since Thursday at 7:12 AM, which is when she verified the RESOLVED status on the portal and closed the case folder for the last time. The verification was a habit, not a need — she had already been told it was resolved by Janelle, who had called at 7:02 AM, before the batch log even processed. But Magda is a care coordinator who was trained before the error-logging systems were as reliable as they are now, back when you verified with your own eyes regardless of what the system said, and she verified.
She has not opened the portal since.
The UPMC-ERR escalation tracker logged RESOLVED at 7:03:47 AM Thursday, June 5, in a batch transaction that included seventeen other case status updates, a scheduled certification renewal for the Allegheny Valley satellite, and a routine synchronization flush from the overnight queue. The log entry for UPMC-ERR-2027-B contains: case identifier, previous status (ESCALATED, tier-3), new status (RESOLVED), timestamp with millisecond precision, processing-node identifier (CHX-BATCH-09), and batch transaction ID. It does not contain Janelle's voice. It does not contain the ceiling Magda watched at 4:10 AM on a Tuesday in April, not the phone call she was waiting for, which didn't come until April wasn't that bad and it was already 4:10 AM in May. It does not contain toast for dinner or the Krakow magnet or the appointment card she had been carrying for three weeks.
Since the RESOLVED timestamp on Thursday, the tracker has processed 23 new escalations. UPMC-ERR-2027-B is not a recent entry. It will remain in the primary log for eighty-nine more days, at which point it will be archived to cold storage and removed from the live query surface. The tracker does not have a category for cases that are resolved. It has a category for cases that are still active and cases that are no longer active. UPMC-ERR-2027-B is in the second category. This is correct. This is what the system is supposed to do.
Field twelve requires pulling the HR portal. She has the login. She has not logged in since February, when she updated her beneficiary address after her sister moved to Bratislava. Logging in tonight would take approximately four minutes: portal load, two-factor authentication, navigation to the insurance subsection, export of the current coverage summary. She knows this because she has logged in enough times to know the navigation by feel. She marks it Monday because Monday is a workday and she will have the portal open for other reasons anyway — the Q3 coordinator review form is due by noon — and doing it Monday takes the same four minutes while she is already in the right context, whereas doing it now on a Saturday requires her to load a professional context she has carefully not loaded today.
She made it through Saturday without loading the professional context. She would like to finish.
Field thirteen is the same portal, different subsection. Previous employer coverage dates for the portability dispute period. She remembers the dates approximately, which is close enough that she could write approximate dates. She marks it Monday because official dates belong on intake forms and approximate dates belong in her head where they have been since the dispute started.
The portability registry dispute is not resolved. She has been aware of this since January, when the cross-registry flagged an overlap in her coverage attribution dates during the care coordinator reassignment period, and since then it has been in administrative review, which is different from UPMC-ERR-2027-B, which was operational. The dispute is bureaucratic. It is not urgent. She has not been receiving medical care that depends on it. It is a form that needs a form that needs a phone call, and the phone call is field fourteen.
Field fourteen: call her previous insurer, request a coverage period summary for the portability dispute documentation. Business hours. She has the insurer's provider coordination line number saved in her work contacts. She will make the call Monday morning, before the Q3 form, and the summary will be faxed or sent to the electronic inbox she set up for the dispute, and she will attach it to the dispute filing, and the registry will update and the dispute will close. She knows every step. She has known every step since January. The steps require Monday.
She is not stuck. She is waiting for Monday.
She clears the dinner bowl and washes it. The kitchen was already clean — she had cleaned it Friday night, after the beets, the first meal she cooked for herself after the escalation resolved, and the cleaning had felt like completing something that started Thursday morning. Now she washes the bowl and puts it away and the kitchen is clean again. It takes three minutes.
From the kitchen she can see the small lamp in the bedroom. She turned it on before dinner. She bought it in March, at the beginning of Q1, when she was in the phase of the escalation that felt like preparation — reading the error logs, building the case structure, learning where the handoff failure actually occurred in the portability chain. She had wanted a lamp with a warm color temperature, something that looked like a lamp and not a task light. It has a timer she set the week she bought it. At 11 PM it turns off automatically.
She set the timer because she kept falling asleep with it on and waking up at 2 AM in the light, which became a problem during the months when waking at 2 AM was followed by checking the escalation tracker from her phone, which she should not have been doing and did anyway. The timer was irrelevant during the worst of it — she was awake at 2 AM regardless, and awake at 3 AM and 4 AM too, and checking the tracker did not help anything and she did it anyway because the tracker was the only thing she could look at that was not the ceiling. The tracker, at 2 AM, was full of cases that were active. None of them were UPMC-ERR-2027-B, which she was the only person tracking, which sometimes felt like a reason to check and sometimes felt like the reason she should stop.
Tonight the timer is relevant again.
She goes back to the couch. The intake form is on the table, folder closed, pen on top. Eleven fields filled. Three remaining. September 4 in six days. She can see the appointment card on the refrigerator from here — the corner of it, beside the Krakow magnet, which is green and yellow and has a small painted rooster. Her mother gave it to her when she moved to Pittsburgh, fourteen years ago. The magnet has held a series of things to the refrigerator in fourteen years: parking reminders, pharmacy slips, Reynek's birthday card from last March when she was going to fly to Bratislava and then didn't. Now it holds the appointment card.
UPMC-ERR-2027-B is RESOLVED in the tracker, in the portal, in the case file, in the Q3 audit queue where it will appear as a closed item and then not appear at all. She could look at the portal right now and confirm this. She confirmed it on Thursday at 7:12 AM and she does not need to confirm it again. She is aware that she knows this and is also aware that the urge to confirm exists separately from the need to, and has been managing both of those things since Thursday and intends to continue.
She thinks about Monday.
Not with dread. This is the thing she noticed this afternoon when she was thinking about the intake form, which was the first time she thought about Monday without a specific anticipation of the escalation being part of it. For three weeks, Monday meant: the escalation is still there. For three weeks, the escalation being there was the organizing fact of Monday. And then RESOLVED was logged and Monday became just Monday again, a day with a Q3 form and a portal login and a phone call to the insurer and a team check-in at 10 AM and a draft report she started Thursday that is already more than half done.
She can see the whole of Monday from Saturday. She has not been able to do that in a while. She is noting it the way you note a thing that has come back: with relief that is quieter than she expected, because she had been trying not to expect anything.
The small lamp will turn off in thirty-eight minutes.
She checks the clock: 10:22 PM. The escalation tracker is processing cases without her watching it. The cross-registry is routing ISF filings and portability disputes and care coordinator transfers through its eleven active nodes, batch by batch, timestamp by timestamp. The portability dispute is in administrative review. It is in the same administrative review it has been in since January and it will still be there Monday morning and the phone call will still work Monday morning and the dispute will close in due course.
She does not know what she will do for the next thirty-eight minutes.
This is a different kind of not-knowing from the not-knowing of the escalation period. That not-knowing was operational: she did not know when the batch error would surface fully, did not know whether the portability chain failure was confined to one handoff point or systemic, did not know whether the 147 patient records in the attribution gap would require individual corrections or a bulk reprocessing. She learned the answers over three months. The answers were hard to get and she got them.
This not-knowing is just Saturday at 10:22 PM. She has thirty-eight minutes and nothing she is supposed to do with them. She sits with this. It is not empty — it does not feel like waiting — it feels like the inside of a thing that has ended correctly. The escalation ended correctly. The beets on Friday ended correctly. The form is eleven of fourteen. Monday is Monday and it has a shape she can see.
The lamp will turn off in thirty-eight minutes whether or not she is in the bedroom.
The tracker is running.
She is on the couch.
Saturday ends on its own.