Public hospitals
Public procurement support
Public procurement support connects hospital requirements with documented consumption, specifications and internal review for procurement and clinical teams. Jovimed organises dossier preparation; the contracting authority determines the procedure and approves documents.
Configuration, integrations and availability are discussed in your demonstration.
FOR
Public procurement teams · Pharmacy and wards · Hospital management
CONTEXT FOR THE TEAM
Law 98/2016: public procurement
Organise records and responsibilities for applicable requirements; competent staff review documents and decisions.
Content reviewed on .
WORKFLOW PREVIEW
Illustrative workflow stages
Conceptual preview · Illustrative data
STAGE 1
The request gains context
The ward records quantities, period and justification together with available evidence.
- Status
- Proposal
- Data
- Illustrative
STAGE 2
Requirements are examined
Procurement and clinical owners examine data, specifications and missing information.
- Status
- Under review
- Data
- Illustrative
STAGE 3
The version is documented
Competent professionals approve documents and determine the next procedural step.
- Status
- Prepared for a decision
- Data
- Illustrative
CAPABILITIES
What the team can follow.
Ward requests need explanation before they become procurement documents. Records follow the source of quantities, assumptions and requirement review. Stock, batches and reserves are a distinct capability; this page focuses on preparation and approval of requirements.
Ward requirements
Associate a request with the ward, period and person providing its justification. Quantities can be examined alongside documented consumption and staff observations before requests are consolidated into a proposed requirement.
Data and assumptions
Distinguish observed values from estimates for future activity. Staff can explain the source, period and assumption behind a quantity so changes in hospital activity can be discussed before documents receive approval.
Specifications for review
Organise functional requirements and supporting documents in a working version. Owners examine necessity, clarity and applicable conditions; software does not select criteria on behalf of the contracting authority.
Associated documents
Connect requisitions, observations and annexes to the relevant requirement. Staff can follow missing documents and identify the version examined, without considering a dossier ready simply because a file has been attached.
Approvals and observations
Retain the reviewer, questions raised and documented approval. A revised request preserves the context of changes, while responsibility for selecting the procurement procedure remains explicit.
Preparation follow-up
Show internal dossier stages and open actions. Teams can prioritise clarifications and prepare a shared view for management; publication and operations in official procurement systems are not presented as automatic.
IN PRACTICE
Two wards request the same material.
Two wards submit similar requirements using different periods and units. Procurement staff review sources before consolidating the requests. A documented comparison helps management understand proposed quantities without turning an estimate into observed consumption.
Owners clarify units and the period covered by each request.
Staff examine available consumption records and explain assumptions for planned activity.
Competent professionals review and approve the consolidated version and specifications.
An explainable requirement and identifiable version of preparation documents, with retained responsibilities and observations.
RECORDS & TRACEABILITY
Records for review.
Requirement documentation follows the path from request to approved version. Data and decisions remain distinct so each proposed quantity can be explained.
- Requests, periods, units and justifications
- Reference consumption and planning assumptions
- Specification versions and review observations
- Owners, approvals and associated documents
BEFORE YOUR DEMONSTRATION
Useful questions.
Does Jovimed automatically publish documents in SEAP?
An automatic publication workflow is not promised. The described capability organises requirements, specifications, documents and internal review. The contracting authority determines the procedure and steps in official systems. Available information and configuration boundaries are discussed during a demonstration so responsibilities for preparation and approval remain clear.
How are proposed quantities justified?
Staff can associate a request with its reference period, unit and documented consumption. Estimates for future activity retain their assumptions and the person who formulated them. Owners examine information before consolidation and approval; a calculated proposal is not treated as evidence of consumption that has already occurred.
Does this include daily inventory management?
Batch, expiry and reserve management has an operational workflow distinct from procurement preparation. Consumption can provide context for requirements when data is available and reviewed. The demonstration clarifies associations between records and team responsibilities so the same information is not assigned inconsistent meanings by different departments.
START WITH A CLEARER PERSPECTIVE
Let’s talk about
your hospital.
Discover how registries, traceability and resource management fit into the way your team works.