For the government and public health management, knowledge about the number of patients suffering from chronic diseases, their consumption of resources, the amount and type of services required by one chronic compared to another and their care burden for primary care is becoming increasingly important.
Information on individual chronic diseases is not always easy to find, since there are no ad hoc information flows. Instead, flows of activity (SDO, pharmaceutical, specialist...), born for administrative purposes, have been consolidated for several years now, which today prove rather suitable for epidemiological as well as economic purposes. You are usually led to think that a person with chronic pathology, most likely, will ask their ASL for assistance the exemption for pathology; in fact, however, and the study on the mapping of chronic diseases confirms this, the database of exemptions cannot be considered exhaustive for this purpose, as often a chronic one, in order to avoid being “labeled” does not require an exemption or this is not required for all chronic diseases of which a person is affected. The intuition was to think that a patient suffering from chronic pathology, requiring a pharmacological treatment and/or hospital admissions and/or special specialist services, could be identified by questioning, according to specific criteria, the information databases of activities. This new study allowed to “recover” more than 50 % of people with chronic illnesses who would otherwise have been unrecognised.
The study data, which are presented in this health report, are only a small part of the multiple results that emerged from the project.
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.