The practice runs on messages. Its records should not.
In a medical practice, requests, results and scheduling arrive as messages all day. Nieme turns them into governed administrative work (documents, follow-ups, the month's close) and leaves every clinical decision with the physician.
What Nieme has observed in the systems you connected. Observations, not instructions — nothing here has been authorized.
The request arrives in the practice's messages.
A document changed in a connected folder.
A message was observed in a selected channel.
A patient asks for a report for work
The request arrives in the practice's messages.
Observed event
- Source
- What happened
- A patient asks for a report for work
- When Nieme saw it
- 12 min ago
Nieme recorded that this event happened. Observation alone authorizes nothing.
Why it matters
Nieme's reason
the source is selected for this Project
Status
Raised as a Signal. Nieme proposes the work; a person decides.
This title is independent of the Objective.
Produces each declared file as a governed Artifact of this one Operation, reviewed together.
Project: Practice · administrative requests
From Signal · a patient message
Selected Operation Sources (3) — explicitly chosen
Practice · administrative requests · operation.on
- DOCXreport-for-employer.docx18 KBproduced
- PDFreport-for-employer.pdf64 KBproduced
Where the work breaks now
Without a record
- The practice runs on chat.Requests, results and scheduling arrive as messages and are handled from memory.
- Paperwork piles up after hours.Reports, forms and letters are written at night, from scattered notes.
- Nobody can show what was sent, and when.A patient asks for a document again, and it is rebuilt from scratch.
With Nieme
- A request becomes work, not a reminder.A message that needs action becomes an administrative task tied to the patient's file.
- Drafted from the practice's own templates.Letters, forms and reports come from the admitted templates and records only.
- The physician decides, on record.Nothing reaches the patient without the physician's approval, and Nieme decides nothing clinical.
From a patient's message to a document the physician signs
-
01 · Observed
A patient asks for a report for work
The request arrives in the practice's messages.
WhatsAppsoon -
02 · Governed
The request is opened as work
Objective, the report template and the patient's file are admitted; nothing else is.
operation.onSources -
03 · Executed
The report is drafted
The report in the practice's own template, with the dates and data already on file.
DOCXPDF -
04 · Reviewed
The physician reviews and signs
Accept, request changes or reject. The physician signs; Nieme never decides anything clinical.
Review -
05 · Carried forward
The file keeps what was issued
When the patient asks again, the issued document and its date are on record.
Evidence
The work outlives the session that did it.
Every step above writes to one record. Swap the model, the agent or the person who executes, and the objective, the sources, the authority and the decision stay attached to the work.
- objective
- Issue a report for the patient's employer
- context
- Report template · the patient's file, admitted for this request only
- authority
- Reviewed and signed by the physician
- executor
- The model the practice chose for documents
- evidence
- The report, the sources it used and the date it was issued
- decision
- Signed by the physician and sent
The fields Nieme stores for every Operation.
Answer patients.
Keep records.
We start with administrative requests only, using your own templates. The physician signs everything, and nothing clinical is decided by Nieme.
Rather talk to a person? Email the founder.