% IMPORTANT: The following is UTF-8 encoded.  This means that in the presence
% of non-ASCII characters, it will not work with BibTeX 0.99 or older.
% Instead, you should use an up-to-date BibTeX implementation like “bibtex8” or
% “biber”.

@ARTICLE{Tremper:169839,
      author       = {G. Tremper$^*$ and T. Brenner$^*$ and F. Stampe$^*$ and A.
                      Borg and M. Bialke and D. Croft$^*$ and E. Schmidt$^*$ and
                      M. Lablans$^*$},
      title        = {{MAGICPL}: {A} {G}eneric {P}rocess {D}escription {L}anguage
                      for {D}istributed {P}seudonymization {S}cenarios.},
      journal      = {Methods of information in medicine},
      volume       = {60},
      number       = {1-02},
      issn         = {0026-1270},
      address      = {Stuttgart},
      publisher    = {Thieme},
      reportid     = {DKFZ-2021-01582},
      pages        = {21-31},
      year         = {2021},
      note         = {#EA:E260#LA:E260# / 2021 May;60(1-02):21-31},
      abstract     = {Pseudonymization is an important aspect of projects dealing
                      with sensitive patient data. Most projects build their own
                      specialized, hard-coded, solutions. However, these overlap
                      in many aspects of their functionality. As any
                      re-implementation binds resources, we would like to propose
                      a solution that facilitates and encourages the reuse of
                      existing components. We analyzed already-established data
                      protection concepts to gain an insight into their common
                      features and the ways in which their components were linked
                      together. We found that we could represent these
                      pseudonymization processes with a simple descriptive
                      language, which we have called MAGICPL, plus a relatively
                      small set of components. We designed MAGICPL as an XML-based
                      language, to make it human-readable and accessible to
                      nonprogrammers. Additionally, a prototype implementation of
                      the components was written in Java. MAGICPL makes it
                      possible to reference the components using their class
                      names, making it easy to extend or exchange the component
                      set. Furthermore, there is a simple HTTP application
                      programming interface (API) that runs the tasks and allows
                      other systems to communicate with the pseudonymization
                      process. MAGICPL has been used in at least three projects,
                      including the re-implementation of the pseudonymization
                      process of the German Cancer Consortium, clinical data flows
                      in a large-scale translational research network (National
                      Network Genomic Medicine), and for our own institute's
                      pseudonymization service. Putting our solution into
                      productive use at both our own institute and at our partner
                      sites facilitated a reduction in the time and effort
                      required to build pseudonymization pipelines in medical
                      research.},
      cin          = {E260},
      cid          = {I:(DE-He78)E260-20160331},
      pnm          = {315 - Bildgebung und Radioonkologie (POF4-315)},
      pid          = {G:(DE-HGF)POF4-315},
      typ          = {PUB:(DE-HGF)16},
      pubmed       = {pmid:34225374},
      doi          = {10.1055/s-0041-1731387},
      url          = {https://inrepo02.dkfz.de/record/169839},
}