Articles
Praemostro - who, what, where, when, why? On this page, you can find frequently asked questions – and read the answers. If you don’t find what you’re looking for, you’re always welcome to contact us.
Overview of the questions answered below:
- What does Praemostro mean?
- How and why was Praemostro founded?
- How long does it take to start seeing forecasts—from the first meeting with Praemostro until graphs and data appear on a screen in our company/ organization?
- Which types of departments can use Praemostro’s system?
- Why is Praemostro’s system smart—what do I gain from using it?
- Are there other systems like Praemostro’s on the market?
- Why not just use regular statistics to predict workload?
- How accurate is Praemostro’s system?
- What do you do when your predictions are off?
- Aren’t you just showing the same graph for every day?
- PraeSight updates continuously throughout the day, but does that even make sense? Isn’t it just showing the same graph over and over?
- What data is required to connect to Praemostro’s system and access forecasts?
- Technically speaking, where do your forecasts run? On your servers or the customer’s own servers?
- Is there a difference in product quality when running on your servers versus our own?
- Do you have an app?
- How many computers can I view my forecasts on?
- In what format should the data be delivered?
- Is our data secure within Praemostro’s system?
- Why are you interested in events?
- Do you work with personally identifiable data?
- Can we add our own data sources to the forecasts?
- Where are your servers physically located?
- What are the typical setup costs (hardware, etc.)?
- How much does it cost to use Praemostro’s system?
- How long am I committed if I subscribe to Praemostro’s forecasts?
- Can I get technical support if the system acts up after installation?
- We’re having trouble obtaining the data needed to set up our forecasts. Can Praemostro’s technicians assist with this?
- Who should I contact for technical support – and how?
About Praemostro and our products
What does Praemostro mean?
How and why was Praemostro founded?
Back in 2016, Mikkel was responsible for research on acute patients at a regional hospital. The management had hired an academic mathematical economist, Troels, who was visiting all departments to introduce himself. Having just read an article about how worsening COPD symptoms were linked to weather conditions, Mikkel challenged Troels to predict the number of patients arriving at the emergency department months in advance.
Troels accepted the challenge and developed a computer model that turned out to be highly accurate (+/- 3% per day, see figure). The project was put on hold as other initiatives took priority. However, in 2021, Odense University Hospital slog innovationsmidler op i 2021, og ideen blev genoptaget og siden udviklet til de produkter, vi har i dag.

How long does it take to start seeing forecasts—from the first meeting with Praemostro until graphs and data appear on a screen in our company/ organization?
Our short-term forecasting solution, PraeSight, takes about one month to set up. Apart from finalizing legal agreements and receiving data from the customer, it takes up to three weeks to develop the first model.
Our long-term forecasting solution, PraePlan, can be delivered quickly with minimal waiting time.
Hvem og hvorfor?
Which types of departments can use Praemostro’s system?
Why is Praemostro’s system smart—what do I gain from using it?
Are there other systems like Praemostro’s on the market?
Why not just use regular statistics to predict workload?
Accuracy?
How accurate is Praemostro’s system?
Our short-term forecast, PraeSight, which predicts 12 hours ahead, has consistently maintained an accuracy of +/- one patient per hour (95% of the time, measured over 8 hours) in a department receiving 75-100 patients per day over nearly three years.
Our long-term forecast, PraePlan, which predicts months in advance, achieves an accuracy of +/- 1-2 patients per hour (93% of the time, measured over 24 hours) in a department handling approximately 130-150 patients per day.
However, it’s important to remember that forecasting, by nature, is never 100% precise. There will always be some margin of error—sometimes more than others. We acknowledge this, but we continuously strive to improve. We actively monitor our systems, and whenever we miss the mark, we investigate, adjust, and refine our models.
What do you do when your predictions are off?
We actively monitor our forecasts to identify days when accuracy is lower than expected. The exact criteria for this can be tailored in collaboration with our customers. When deviations occur, we investigate: Was there an event we didn’t account for? Were there weather conditions we hadn’t factored in? Or was it something else entirely? If we cannot find an explanation ourselves, we engage in dialogue with the customer. Our entire ethos is built on making a difference for people who make a difference for others—something we can only achieve by always doing our best.
Aren’t you just showing the same graph for every day?
Of course, there is a general pattern in patient arrivals. In emergency departments worldwide, Mondays and Fridays are typically the busiest days, and the afternoon and early evening are the most active times. However, no two days are identical. Some days are much busier, while others are quieter.
That’s where our system makes a difference. Knowing in advance whether a particular day will be busy or slow allows for better staffing decisions—ensuring both cost-effective and resource-efficient management.
We’ve compiled data from multiple Mondays in one of the emergency departments we work with to illustrate how no two days are the same. The graphs show the expected number of patients over a 12-hour period, starting at 7 AM.
PraeSight updates continuously throughout the day, but does that even make sense? Isn’t it just showing the same graph over and over?
It might seem that way, but that’s not the case. Our models update dynamically as new data comes in—whether from patient counts, weather forecasts, or other sources. This means the system becomes increasingly refined and accurate throughout the day. Below, you can see an example of how the forecast graphs evolve hour by hour over a single day.
Technology and security
What data is required to connect to Praemostro’s system and access forecasts?
Technically speaking, where do your forecasts run? On your servers or the customer’s own servers?
Is there a difference in product quality when running on your servers versus our own?
Do you have an app?
How many computers can I view my forecasts on?
In what format should the data be delivered?
We have created a technical documentthat describes this in detail. However, in simple terms, we need a file that includes timestamps and counts for what needs to be forecasted, such as: 01-01-2023 08:00-08:59, 23; 01-01-2023 09:00-09:59, 45; etc. Additionally, we require a file with events that may influence the expected number of patients. Of course, we are happy to assist if needed.
Is our data secure within Praemostro’s system?
Is our data secure within Praemostro’s system?
Why are you interested in events?
Over the years, we have observed that certain events significantly impact demand in the environments where our forecasts are used. Some events are obvious—such as a large concert near an emergency department, which leads to increased patient intake. Others are more surprising; for example, we have seen a decrease in emergency visits on days when Donald Trump was up for election.
Some events can be anticipated on our end and incorporated into the system (e.g., major sporting events, festivals), while others require local knowledge, meaning the customer must help us identify them.
Adding events to our system is quick and straightforward, but it must be done continuously. At the same time, we regularly test our forecasts to refine our understanding of which events truly matter. Some might not require monitoring, while others may need to be added to the list.
Do you work with personally identifiable data?
Our forecasts are based solely on the number of arrivals within a given time frame, such as "12 people arrived between 1 PM and 2 PM." This data is not inherently personally identifiable. However, due to regulations, we establish a data processing agreement with our customers. Since we access the customer’s IT systems, there is a theoretical possibility of identifying individuals. When entering into a contract with Praemostro, we will sign a data processing agreement—either using the customer’s version or our own, which is based on the Danish Data Protection Agency’s standard contract.
Can we add our own data sources to the forecasts?
Where are your servers physically located?
Economy
What are the typical setup costs (hardware, etc.)?
How much does it cost to use Praemostro’s system?
How long am I committed if I subscribe to Praemostro’s forecasts?
Support
Can I get technical support if the system acts up after installation?
We’re having trouble obtaining the data needed to set up our forecasts. Can Praemostro’s technicians assist with this?
Who should I contact for technical support – and how?
You can call our main number at 25 56 30 20 or email us at support@praemostro.com.
Want to take a look into the future together?
Get in touch and we’ll get back to you as soon as possible
