Use of intravenous iron and risk of anaphylaxis: A multinational observational post-authorisation safety study in Europe

PURPOSE

This post-authorisation safety study estimated the risk of anaphylaxis in patients receiving intravenous (IV) iron in Europe, with interest in iron dextran and iron non-dextrans. Studies conducted in the United States have reported risk of anaphylaxis to IV iron ranging from 2.0 to 6.8 per 10 000 first treatments.

METHODS

Cohort study of IV iron new users, captured mostly through pharmacy ambulatory dispensing, from populations covered by health and administrative data sources in five European countries from 1999 to 2017. Anaphylaxis events were identified through an algorithm that used parenteral penicillin as a positive control.

RESULTS

A total of 304 210 patients with a first IV iron treatment (6367 iron dextran), among whom 13-16 anaphylaxis cases were identified and reported as a range to comply with data protection regulations. The pooled unadjusted incidence proportion (IP) ranged from 0.4 (95% confidence interval [CI], 0.2-0.9) to 0.5 (95% CI, 0.3-1.0) per 10 000 first treatments. No events were identified at first dextran treatments. There were 231 294 first penicillin treatments with 30 potential cases of anaphylaxis (IP = 1.2; 95% CI, 0.8-1.7 per 10 000 treatments).

CONCLUSION

We found an IP of anaphylaxis from 0.4 to 0.5 per 10 000 first IV iron treatments. The study captured only a fraction of IV iron treatments administered in hospitals, where most first treatments are likely to happen. Due to this limitation, the study could not exclude a differential risk of anaphylaxis between iron dextran and iron non-dextrans. The IP of anaphylaxis in users of penicillin was consistent with incidences reported in the literature.

Modeling Requirements for Cohort and Register IT

BACKGROUND

The project KoRegIT (funded by TMF e.V.) aimed to develop a generic catalog of requirements for research networks like cohort studies and registers (KoReg). The catalog supports such kind of research networks to build up and to manage their organizational and IT infrastructure.

OBJECTIVES

To make transparent the complex relationships between requirements, which are described in use cases from a given text catalog. By analyzing and modeling the requirements a better understanding and optimizations of the catalog are intended. There are two subgoals: a) to investigate one cohort study and two registers and to model the current state of their IT infrastructure; b) to analyze the current state models and to find simplifications within the generic catalog.

METHODS

Processing the generic catalog was performed by means of text extraction, conceptualization and concept mapping. Then methods of enterprise architecture planning (EAP) are used to model the extracted information. To work on objective a) questionnaires are developed by utilizing the model. They are used for semi-structured interviews, whose results are evaluated via qualitative content analysis. Afterwards the current state was modeled. Objective b) was done by model analysis.

RESULTS

A given generic text catalog of requirements was transferred into a model. As result of objective a) current state models of one existing cohort study and two registers are created and analyzed. An optimized model called KoReg-reference-model is the result of objective b).

CONCLUSION

It is possible to use methods of EAP to model requirements. This enables a better overview of the partly connected requirements by means of visualization. The model based approach also enables the analysis and comparison of the empirical data from the current state models. Information managers could reduce the effort of planning the IT infrastructure utilizing the KoReg-reference-model. Modeling the current state and the generation of reports from the model, which could be used as requirements specification for bids, is supported, too.

Requirements and tasks of cohorts and registers, the German KoRegIT project

Epidemiological cohorts and registers (KoReg) are long lasting and complex research projects, which need systematic and extensive planning and steering. The aim of the KoRegIT project was to develop a generic catalogue of requirements to support the organisational- and IT-structure of KoReg. The catalogue of requirements comprises the top level (TL) tasks of the core processes. All TL were classified into the following project phases: 1. Development, 2. Operation, 3. Completion. According to the defined TL tasks, the appropriate use cases (UC) were identified. The catalogue currently specifies 45 TL tasks and 207 UC. The UC were elaborated by a short and standardized description of the task, the involved actors (human or external systems), the preconditions, which have to be fulfilled in order to realize this task, the normal flow of the task and the post conditions. The developed catalogue was reviewed by representatives of different KoReg in Germany. The draft catalogue of requirements was revised according to the reviewer's feedback and discussion. The revised and complete catalogue with all elaborated UC was reviewed again by further experts. The developed KoRegIT catalogue of requirements offers a supporting tool to set-up the organisational structures and processes of KoReg as well as the definition of the needed IT-infrastructure. In addition it can be used to optimize or to expand these structures.