<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Towards a Medication Core Data Set for the Medical Informatics Initiative (MII): Initial Mapping Experience between the German Procedure Classification (OPS) and the Identification of Medicinal Products (IDMP)</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Susanne ZABKA</string-name>
          <email>susanne.zabka@imbi.uni-freiburg.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff5">5</xref>
          <xref ref-type="aff" rid="aff9">9</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Danny AMMON</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff9">9</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Thomas GANSLANDT</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
          <xref ref-type="aff" rid="aff9">9</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jan GEWEHR</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff6">6</xref>
          <xref ref-type="aff" rid="aff9">9</xref>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>Freiburg, Germany</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>&amp; IT Department, Jena University Hospital</institution>
          ,
          <addr-line>Jena</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Christian HAVERKAMP</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Data Integration Center, Institute of Medical Statistics</institution>
          ,
          <addr-line>Computer and Data Sciences</addr-line>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Freiburg</institution>
          ,
          <addr-line>Freiburg</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>Heinrich-Lanz-Center for Digital Health, University Medicine</institution>
          <addr-line>Mannheim</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff5">
          <label>5</label>
          <institution>Institute for Medical Biometry and Medical Informatics, University of Freiburg</institution>
        </aff>
        <aff id="aff6">
          <label>6</label>
          <institution>Research IT, University Medical Center Hamburg-Eppendorf</institution>
          ,
          <addr-line>Hamburg</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff7">
          <label>7</label>
          <institution>Staff Unit IT-Processes, Faculty of Medicine and Medical Center, University of</institution>
        </aff>
        <aff id="aff8">
          <label>8</label>
          <institution>Staff Unit Research Support, Department IT, University Hospital of Tuebingen</institution>
        </aff>
        <aff id="aff9">
          <label>9</label>
          <institution>University</institution>
          ,
          <addr-line>Leipzig</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Documentation of medication processes is among the most difficult tasks associated with digital clinical documentation. Despite its great potential medical impact, it has not been consistently adopted in German university hospitals, with one of the reasons being the lack of a comprehensive information model with sound terminological support. With the Identification of Medicinal Products (IDMP), several international authorities have recently provided a comprehensive set of standards for the formal description of drugs, mainly for regulatory purposes. In this paper, we describe the approach of the German Medical Informatics Initiative (MII) towards the modelling of a medication core dataset using IDMP. Three different process models with minimal datasets for medication were defined: summative documentation of episodes, point-wise documentation, and medication plans (snapshot documentation). As a feasibility</p>
      </abstract>
      <kwd-group>
        <kwd>and the Identification of Medicinal</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>study evaluating how standard terminologies can be used for a minimal data set of
hospital medication data, a mapping between IDMP terminologies and the
medication chapter of the German Procedure Classification “OPS”
(Operationenund Prozedurenschlüssel) was developed. About 1700 OPS classes, representing
about 160 highly reimbursement relevant drugs, were mapped onto different axes
of IDMP (substances, optionally: routes of administration and units) using several
coding systems with different scopes, to analyze their coverage and particular
advantages. A mapping was possible for almost all OPS codes. For the substances,
it is necessary to distinguish between the common substance name and the active
ingredient, as these may be different for a drug. This “lightweight” mapping
approach demonstrates the basic feasibility of using IDMP for medication
documentation.</p>
    </sec>
    <sec id="sec-2">
      <title>1. Introduction</title>
      <p>Electronic documentation of medication processes is among the most difficult tasks
associated with digital clinical documentation. Despite its great potential medical
impact e.g. for patient safety, it has not been consistently adopted in German university
hospitals. Besides complex and divergent medical processes, the lack of a
comprehensive information model with sound terminological support has hindered the
development of interoperable documentation systems in this domain. A first step in
2016 was the introduction of the right to receive a structured medication plan for
insured patients who are using at least three prescribed drugs at the same time. With the
Identification of Medicinal Products (IDMP), several international authorities, e.g. the
European Medicines Agency (EMA), the Food and Drug Administration (FDA), and
the International Organisation for Standardisation (ISO), have recently provided a
comprehensive set of standards for the formal description of drugs and other medicinal
products mainly for regulatory purposes.</p>
      <p>In this paper, we describe the approach of the German Medical Informatics
Initiative (MII) towards the modelling of a medication core dataset based on IDMP and
a feasibility study evaluating how standard terminologies can be used for hospital
medication data using a minimum data set available in all German hospitals.</p>
    </sec>
    <sec id="sec-3">
      <title>2. Background</title>
      <p>
        The Medical Informatics Initiative (MII) was launched by the German Federal Ministry
of Education and Research (BMBF), with the goal of developing infrastructure for the
integration of clinical data from patient care and medical research in Germany. Four
consortia consisting of university hospitals and other institutions communicate and
collaborate under the guidance of the national steering committee. This includes the
consistent use of international standards to ensure interoperability [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and
maintaining a core data set in each university hospital as a minimum requirement for
patient data [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. For medication in the hospital, these data can be collected by all
inpatient care facilities based on the codes for medications eligible for supplemental
reimbursement [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. The German procedure classification OPS (Operationen- und
Prozedurenschlüssel) is the official classification system in the German health system
for the reimbursement of surgeries and other medical interventions [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. OPS is an
adaptation of the World Health Organisation (WHO) International Classification of
Procedures in Medicine (ICPM) [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], developed and maintained by the DIMDI (German
Institute of Medical Documentation and Information). The OPS list consists of
alphanumeric codes assigned to each intervention. It includes a section on medication
(chapter 6) with more than 1600 codes representing about 160 highly
reimbursementrelevant drugs. These codes have different levels of granularity, but in most cases they
stand for the application of a defined amount of a drug, for example:
      </p>
      <sec id="sec-3-1">
        <title>Code 6-006.bf: “Parenteral application of 50 mg up to 75 mg Brentuximabvedotin”</title>
        <p>The OPS codes are mandatory in all hospitals in Germany and are essential in
order to determine the DRG (diagnosis related groups) code and therefore for billing.
They can be used to extract information about the active substance applied to a patient
in a certain episode (period of hospitalisation) in a standardized way.</p>
      </sec>
      <sec id="sec-3-2">
        <title>2.1. Information models for medication</title>
        <p>
          In the United States, RxNorm [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] is an information model for medication already in
existence for several decades and which is often cited as a standard drug terminology
[25]. It is a tool for supporting semantic interoperation between drug terminologies and
pharmacy knowledge base systems. The National Library of Medicine (NLM) produces
RxNorm and provides it via the UMLS Terminology Services [26].
        </p>
        <p>Term types are used to indicate generic and branded drug names at different levels of
specificity, and relationships link concepts which contain the same ingredient or dose
form. In addition to normalized names and relationships, attributes like unique
identifiers are associated with a concept, for example, unique ingredient identifiers
(UNIIs) or national drug codes (NDCs) [26].</p>
      </sec>
      <sec id="sec-3-3">
        <title>2.2. The international standard for the Identification of Medicinal Products (IDMP)</title>
        <p>
          While RxNorm is an information model specific to the US, ISO IDMP came from a
need to standardise the definition of medicinal product information globally, initially in
the context of pharmacovigilance activities, and later expanded to regulatory activities
and healthcare practices such as the prescription and dispensation of medicines [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. To
ensure wide interoperability across global regulatory and healthcare communities, these
standards were developed and published under the auspices of the ISO (International
Organization for Standardization), with input from the International Council for
Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH),
Health Level Seven (HL7) and other international stakeholders and experts [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ].
        </p>
        <p>The ISO IDMP comprises five separate standards published in 2012 which
establish definitions and concepts, and describe data elements and their structural
relationships to uniquely identify and exchange information on:
• substances (ISO 11238);
• pharmaceutical dose forms, units of presentation, routes of administration and
packaging (ISO 11239);
• units of measurement (ISO 11240);
• regulated pharmaceutical product information (ISO 11616);
• regulated medicinal product information (ISO 11615).</p>
        <p>
          These standards cover the following aspects of describing a medicinal product for
human use: medicinal product name, ingredient substances, pharmaceutical product
(route of administration, strength), marketing authorization, clinical particulars,
packaging and manufacturing [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ], [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ].
        </p>
        <p>
          In the EU, the European Medicines Agency (EMA) is implementing the IDMP
standards in a phased program based on the four domains of master data in
pharmaceutical regulatory processes: substance, product, organisation and referential
(SPOR) master data [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. Of these, the Referentials Management Service was launched
in June 2017 to supply master data to the electronic application forms [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ], [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] and
contains over a hundred lists of controlled vocabularies to describe attributes of
products, e.g. lists of dosage forms, units of measurement and routes of administration.
These include the lists of standard terms of the European Directorate for the Quality of
Medicines and HealthCare (EDQM) of the Council of Europe, corresponding to ISO
11239 and ISO 11240 [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. For the substances, it was decided to use and adapt G-SRS
(a global substance registration system developed by the FDA in collaboration with
several European experts) as a basis and adapt it to European requirements (EU-SRS) [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
        </p>
        <p>While IDMP has its origin mainly in the regulatory context, the implementation of
the standard models and terminology will be also extremely useful for modelling
medication processes in the hospital context.</p>
      </sec>
      <sec id="sec-3-4">
        <title>2.3. Standard vocabularies in the pharmaceutical context</title>
        <p>The IDMP ISO standards provide a conceptual framework including definitions, data
elements and structures as well as examples of vocabularies or identifiers, but do not
specify which terminology has to be used in each case. Therefore, some existing
vocabularies are described in the following table:</p>
        <sec id="sec-3-4-1">
          <title>The Chemical Abstracts Service (CAS) Chemical Registry System, operating since 1965, uniquely identifies chemical substances on the basis of molecular structure [15].</title>
          <p>Vocabulary or coding system
(abbreviation, meaning, format)
substances, ISO 11238
UNII
(Unique Ingredient Identifier)
Unique alphanumeric code for
substances used in drugs, ISO 11238</p>
        </sec>
        <sec id="sec-3-4-2">
          <title>ATC code</title>
          <p>
            (Anatomical Therapeutic Chemical)
Alphanumeric code for the
pharmacological, therapeutic and chemical
properties of a substance or substance
combination used in a drug
EDQM Standard Terms
(European Directorate for the Quality
of Medicines and Health Care)
standard vocabulary and associated
code for the pharmaceutical dosage
forms, routes and/or methods of
administration and others, mainly in
the context of drug registration, ISO
11239
UCUM codes
(Unified Code for Units of Measure)
code and description for units of
measure, ISO 11240
Details
UNIIs are generated by the US Substance Registration System
and are part of the RxNorm described above [
            <xref ref-type="bibr" rid="ref16">16</xref>
            ]. The GINAS
(Global Ingredient Archival System) project now establishes a
global information system for pharmaceutical ingredients,
called G-SRS (global substance registration system). It
provides a common identifier for all of the substances used in
medicinal products, utilizing a consistent definition of
substances globally, including active substances under clinical
investigation, consistent with the ISO 11238 standard [17].
In the ATC classification system provided by the WHO, active
substances are classified into a hierarchy with five different
levels with anatomical/pharmacological groups at the highest
level, further divided into chemical, pharmacological or
therapeutic subgroups and the chemical substance on the 5th
level [18]. In Germany, the DIMDI publishes the annually
updated official version of the German Anatomical
Therapeutic Chemical (ATC) classification [19] which is also
available as an Excel file compiled by the scientific institute of
a health insurance company [20].
          </p>
        </sec>
        <sec id="sec-3-4-3">
          <title>The European Directorate for the Quality of Medicines and</title>
          <p>Health Care (EDQM) is a directorate of the Council of Europe
ensuring the quality and safety of medicines. They offer a
standard terms database with over 900 terms in 34 world
languages, to be used in European marketing authorisation
applications as standard vocabulary for the pharmaceutical dosage
forms, routes and/or methods of administration, units of
presentation, and containers, closures and delivery devices [22].</p>
        </sec>
        <sec id="sec-3-4-4">
          <title>Code system intended to be able to construct all units of measures contemporarily used in international science, engineering, and business [24].</title>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>3. Methods</title>
      <p>The Interoperability Working Group of the National Steering Committee of the MII
created an inter-disciplinary taskforce to define a core module for medication
documentation, intended for the interoperable exchange/analysis of medication data
throughout German university hospitals. All decisions are reached by consensus among
the four participating consortia. The levels of documentation of the medication process
in the clinical setting were analysed with regard to their timing and associated data.
Based on this, different process models with minimal datasets and suitable options for
their terminological representation were developed.</p>
      <p>
        To investigate the feasibility of a formal representation of a medication process, a
mapping between IDMP terminologies and the German Procedure Classification (OPS),
chapter 6 (medication) was developed. The OPS codes related to medication were
selected for the first study as they are mandatory for billing and thus available at each
hospital. They were downloaded from the DIMDI homepage [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] into a Microsoft Excel
table. For each OPS expression, the substance name, the information related to the
dosage form or administration route and to the amount and unit of substance was
extracted manually. These expressions were mapped to the standard terminologies (c.f.
figure 1) and added to the Excel table.
      </p>
      <p>6-006.bf Parenteral</p>
      <p>application
Component OPS-Code [application] [minimum [maximum [unit]
of the OPS- amount] amount]
code
Example of 50 […] up to 75 Mg
Active
substance
Brentuximab
vedotin
[additional
active
substance(s)]
[Additional
information]
Mapping:</p>
      <p>¯
Mapping to N/A
(if possible):</p>
      <p>¯
EDQM
standard terms:
Route of
administration
and/or
intended site
and/or
application
method
¯
¯
¯
¯
¯
¯
Number</p>
      <p>Number</p>
      <p>UCUM</p>
      <p>N/A
WHO INN WHO INN
and and
ASK number ASK number
and and
CAS number CAS number
and and
UNII code UNII code
and and
ATC code ATC code</p>
      <p>
        OPS: Operationen- und Prozedurenschlüssel (German procedure classification) [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]
EDQM: European Directorate for the Quality of Medicines, standard terms for: Intended Site [27],
Administration Method [27] and Routes and Methods of Administration [28]
UCUM: Unified Code for Units of Measure [24]
WHO INN: World Health Organisation International Nonproprietary Name [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]
ASK number: Arzneistoffkatalog (German drug substances catalogue) number [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]
CAS number: Chemical Abstracts Service number taken from [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] and partly from [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]
UNII code: Unique Ingredient Identifiers code [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]
      </p>
      <p>ATC code: Anatomical Therapeutic Chemical code [20],
N/A: not applicable, in brackets []: expression not part of all OPS codes</p>
    </sec>
    <sec id="sec-5">
      <title>4. Results</title>
      <p>The MII defined a core data set for the representation of clinical medication processes.
To represent the different approaches and capabilities of sites with regard to structured
medication documentation, three “levels” of documentation were defined: summative
documentation of episodes, point-wise documentation, and snapshot documentation
(medication plans, discharge medication). The levels differ in their references to time
and in the comprehensiveness of their data sets.</p>
      <p>The summative documentation of episodes describes the medication applied to a
patient during a hospital stay. This includes the substance, the start and end date of the
medication episode and optionally the product, the amount of substance and dosing
information.</p>
      <p>The point-wise documentation describes the medication applied at a given point
in time and includes information about the substance, the application time (or start and
end time), the dosage and optionally also the drug product and route of administration.</p>
      <p>The snapshot documentation describes medication plans or the discharge
medication with the drug name, the dosing scheme and strength and optionally the
substance.</p>
      <p>Mapping
example:
Mapped to
Code: value</p>
      <sec id="sec-5-1">
        <title>4.1. Mapping of OPS codes</title>
        <p>For the summative documentation of episodes, the OPS codes available at all German
hospitals can be used to extract the medication data for all reimbursement relevant
drugs. A mapping table was created representing all 1630 medication-related OPS
codes. The list downloaded from the official site contains 1668 rows as several OPS
codes were listed with two or more meanings or with different expressions for the same
drug.</p>
        <p>The following table 1 is an example of a complete set of mapping information for
one OPS code.
*) The substance name has a different spelling in WHO INN, ASK and ATC.
**) In this case, only the “intended site” could be derived from the expression used in the OPS code. The
values for the “route of administration” and “administration method” were looked up in registration
information</p>
        <p>The mapping of the active substances was possible for almost all OPS codes and is
described in more detail in the next chapter.</p>
        <p>The mapping of additional information included in many of the OPS codes was
optional according to the requirements in the data set for the summative documentation
of episodes. The following mapping was performed:
• Amount of drug: For all OPS code expressions containing a unit, the
mapping to a UCUM code was possible. The corresponding UCUM codes and
UCUM descriptions, as well as the minimum and maximum amount of drug
Active [Active
substance substance]
Brentuximabve N/A
dotin *)</p>
        <p>N/A
WHO INN:
Brentuximab
vedotin *)
ASK number:
39958
CAS number:
914088-09-8
UNII code:
7XL5ISS668
ATC code:
L01XC12
•
•
as listed in the OPS codes, were added to the table. The units used in the table
are gram, milligram, microgram, international unit and Giga-Becquerel.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Application or Route of administration: OPS codes often contain</title>
      <p>expressions like “parental application of…” or “oral application of …” for
drug administration. In these cases a mapping to the long established lists of
EDQM standard terms for the “routes and methods of administration” was
intended. However, a unique mapping of the application form is difficult in
many cases, as the expressions in the OPS codes are rather unspecific and the
data model used for the EDQM standards terms is much more specific. Here,
the EDQM terminology distinguishes between terms for “Intended Site”,
“Administration Method” and “Routes and Methods of Administration”. As
an example, the expression “parental application”, which can be found in
many OPS codes, would be coded with the EDQM terminology “intended
site”= “parenteral”, whereas the EDQM application method and EDQM routes
and methods of administration are not clearly defined. In most cases, the
expression in the OPS code could be clearly mapped to the EDQM “intended
site” (e.g. “parenteral”, “oral”), but sometimes it corresponded to the EQDM
„Routes and Methods of Administration“ (e.g. “intrathecal application” or
“implantation”).</p>
    </sec>
    <sec id="sec-7">
      <title>Information related to the drug product: The OPS codes contain almost no</title>
      <p>information about the dosage form of the drug product, therefore no mapping
was performed.</p>
      <sec id="sec-7-1">
        <title>4.2. Mapping of the active substance</title>
        <p>Three OPS codes could not be mapped as they are not related to a unique substance.
The remaining 1627 OPS codes comprise 155 drugs with one active substance and
seven drugs with combinations of two or more active substances. Altogether 166
individual substances, including those substances that were only included as a
component of the combination drugs, were mapped to the WHO INN name, the
German ASK number, the UNII number and the CAS number. For the combination
products, this mapping was performed for each individual substance.</p>
        <p>ATC codes are assigned to combination products as well, therefore the mapping
contains the ATC codes for 162 substances or substance combinations.</p>
        <p>During the mapping procedure we encountered several instances of different
numbers for the substance and its derivatives due to the fact that the substance’s
common name (e.g. INN name) is not always identical to the drug’s active ingredient,
which may be a salt or other preparation (e.g. INN name „Doxorubicin” with active
ingredient „Doxorubicin hydrochloride“, or INN “liposomal Irinotecan” with active
ingredient “Irinotecanhydrochlorid trihydrate”). This difference between the active
ingredient, which is only listed in the registration information, and the “commonly used”
INN expression, is usually not obvious from the OPS list or the drug name.</p>
        <p>The mapping was adapted to both include codes for the substance´s common name
and for the derivatives representing the active ingredient of the drug, if applicable.</p>
        <p>Table 3 summarizes the kinds of mappings and the number of codes found.</p>
      </sec>
    </sec>
    <sec id="sec-8">
      <title>5. Summary and discussion</title>
      <p>The mapping table is a useful tool to compare different terminologies for the coding of
drugs based on the limited information available in the OPS codes. It also demonstrates
the advantages and disadvantages of the terminologies used.</p>
      <p>An important aspect to be considered in coding the individual substances is the
distinction between “substance” in the sense of the generic name (WHO INN,
“ingredient” in RxNorm terminology) as opposed to the “active ingredient”, which may
be a derivative of the substance in some cases (WHO modified INN, “precise
ingredient” in RxNorm terminology [26]) . This difference may not be known to a
nonexpert and the active ingredient is usually not obvious from the common name
routinely used. However, the active ingredient (or the code representing it) is listed in
the registration information and in drug databases containing this information. For the
retrieval of substances, possible solutions may either be to link the “related” substances
and/or establish a convention to always use the number of the generic substance,
accepting the inaccuracy at the chemical level.</p>
      <p>None of the coding systems or terminologies used in this feasibility study could be
used to unambiguously code each of the 166 individual substances (see table 3),
however the coverage was above 99%. In addition, some inconsistencies related to the
CAS numbers listed in the other substance lists were discovered.</p>
      <p>The ATC codes have a different scope as they are mainly intended to identify the
pharmaceutical and therapeutic area. Therefore they also provide identifiers for
combination products. However, not all ATC codes are unique to a substance as these
drugs are used for several indications. While the possibility of distinguishing between
therapeutic areas may even be an advantage for retrieval, it would require the proper
ATC code to be entered each time such a medication is given, which may be difficult in
the clinical daily routine.</p>
      <p>As the OPS codes do not contain sufficient information to allow an unambiguous
mapping to the dosage form and even the route of administration cannot be mapped
unambiguously to a common vocabulary, the presented mapping table only includes
the EDQM terms as an example of how these terms would be applied to drug products.</p>
      <p>The mapping in this list is specific to Germany, as it is based on German billing
codes and the German drug catalog (ASK numbers). The OPS codes may evolve,
therefore the mapping lists need to be checked and potentially adapted every year.</p>
      <p>This mapping can only be used for the limited number of drugs included in the
OPS codes. It is not feasible to perform the same mapping manually for all available
drugs, therefore it will be necessary to check how the data model is structured in
registration information systems like AMIS, commercial drug databases like
ABDATA2 or in the medication management solution of hospital information systems,
and whether this can be used. In some hospital systems a specific coding of drugs may
already be available, e.g. ATC.</p>
    </sec>
    <sec id="sec-9">
      <title>6. Conclusion</title>
      <p>The recent introduction of IDMP has provided a sound information model with strong
terminological support. Although mainly intended for the description of drugs and
other medicinal products in a regulatory context, the MII has adopted IDMP for the
documentation of clinical medication processes.</p>
      <p>The integrated use of IDMP standards combined with other terminologies and
ontologies (e.g. SNOMED CT) in interoperable technical standards like HL7 FHIR
enables a comprehensive description of medication processes and entities.</p>
      <p>A “lightweight” approach based on a mapping between IDMP and the OPS
demonstrated the basic feasibility of the approach presented here. The use of OPS
codes has the advantage that all university hospital cases are already OPS-coded due to
their role in the billing system for hospital stays. In future, however, a much more
precise and comprehensive description of the medication processes will be necessary.
An information model covering all three levels of the medication data set, and more
formal specifications using the FHIR (Fast Healthcare Interoperability Resources)
format are currently being developed within the framework of the Medical Informatics
Initiative and will be successively introduced at the sites.</p>
      <p>2 https://abdata.de/datenangebot/abda-datenbank/</p>
    </sec>
    <sec id="sec-10">
      <title>Acknowledgements</title>
      <p>This study was funded by the German Federal Ministry of Education and Research
(BMBF) within the ‘‘Medical Informatics Funding Scheme’’ (FKZ 01ZZ1801X, FKZ
01ZZ1802X, FKZ 01ZZ1803X, FKZ 01ZZ1804X). We would like to thank James
Balmford for English proof-reading.
[17] U.S. Department of Health &amp; Human Services National Institutes of Health, “The Ginas Project.” 2019
[Online]. Available: https://tripod.nih.gov/ginas/#/. [Accessed: 14-May-2019]
[18] WHO Collaborating Centre for Drug Statistics Methodology, “ATC Structure and principles.” 2019
[Online]. Available: https://www.whocc.no/atc/structure_and_principles/. [Accessed: 08-May-2019]
[19] Deutsches Institut für Medizinische Dokumentation und Information (DIMDI), “ATC-Klassifikation
mit definierten Tagesdosen DDD.” 2019 [Online].</p>
      <p>Available: https://www.dimdi.de/dynamic/de/arzneimittel/atc-klassifikation/. [Accessed: 08-May-2019]
[20] Wissenschaftliches Institut der AOK, “ATC-Klassifikation für den deutschen Arzneimittelmarkt.” 2019
[Online].</p>
      <p>Available: https://www.wido.de/publikationen-produkte/arzneimittel-klassifikation/. [Accessed:
08May-2019]
[21] European Directorate for the Quality of Medicines and HealthCare (EDQM), “Factsheet: Reference
Standards in Europe.” 01-Jun-2018 [Online].</p>
      <p>Available: https://www.edqm.eu/sites/default/files/factsheet_pheur_reference_standards_june_2018.pdf.
[Accessed: 09-May-2019]
[22] European Directorate for the Quality of Medicines and HealthCare (EDQM), “Standard Terms
Database.” [Online]. Available: https://www.edqm.eu/en/standard-terms-database. [Accessed:
09-May2019]
[23] European Directorate for the Quality of Medicines and HealthCare (EDQM), “Standard Terms.” 2019
[Online]. Available: https://standardterms.edqm.eu/. [Accessed: 15-May-2019]
[24] G. Schadow and C. J. McDonald, “The Unified Code for Units of Measure.” 21-Nov-2017 [Online].</p>
      <p>Available: http://unitsofmeasure.org/ucum.html#datyp2apdxatblxmp. [Accessed: 08-May-2019]
[25] O. Bodenreider, R. Cornet, and D. J. Vreeman, “Recent Developments in Clinical Terminologies</p>
      <p>SNOMED CT, LOINC, and RxNorm,” Yearb. Med. Inform., vol. 27, no. 1, pp. 129–139, Aug. 2018.
[26] US National Library of Medicine, “RxNorm Overview.” [Online]. Available:
https://www.nlm.nih.gov/research/umls/rxnorm/overview.html. [Accessed: 09-May-2019]
[27] European Directorate for the Quality of Medicines and HealthCare (EDQM), “EDQM Standard Terms,
Internal controlled vocabularies for pharmaceutical dose forms, Version 1.2.0 – 28 January 2019.” 2019
[Online].</p>
      <p>Available:https://www.edqm.eu/sites/default/files/standard_terms_internal_vocabularies_for_pharmace
utical_dose_forms.pdf. [Accessed: 15-Oct-2018]
[28] European Directorate for the Quality of Medicines and HealthCare (EDQM), “Standard Terms, Routes
and Methods of Administration (restricted access).” 2019 [Online].</p>
      <p>Available: https://standardterms.edqm.eu/browse/get_concepts/ROA. [Accessed: 15-Oct-2018]</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>S. C.</given-names>
            <surname>Semler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Wissing</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Heyder</surname>
          </string-name>
          , “German Medical Informatics Initiative,”
          <source>Methods Inf. Med</source>
          ., vol.
          <volume>57</volume>
          , no.
          <source>S 01</source>
          , pp.
          <fpage>e50</fpage>
          -
          <lpage>e56</lpage>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <article-title>[2] German medical informatics initiative</article-title>
          , “Medical Informatics Initiative Germany.” 2019 [Online]. Available: https://www.medizininformatik-initiative.de/en/start. [Accessed:
          <fpage>14</fpage>
          -May-2019]
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <article-title>[3] German medical informatics initiative, “Core data set</article-title>
          .”
          <year>2019</year>
          [Online]. Available: https://www.medizininformatik-initiative.de/en/core-data-set. [Accessed:
          <fpage>15</fpage>
          -May-2019]
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Medical</given-names>
            <surname>Informatics</surname>
          </string-name>
          <string-name>
            <surname>Initiative</surname>
          </string-name>
          , “
          <article-title>MII Core Data Set. Draft from the Core Data Set Drafting Group</article-title>
          ,” Mar.
          <year>2017</year>
          [Online]. Available:https://www.medizininformatik-initiative.de/sites/default/files/inline files/MII_04_Core_Data_Set_
          <fpage>1</fpage>
          -
          <lpage>0</lpage>
          .pdf. [Accessed:
          <fpage>15</fpage>
          -May-2019]
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <article-title>[5] DIMDI, “OPS (Operationen- und Prozedurenschlüssel)</article-title>
          .” 2019 [Online]. Available: https://www.dimdi.de/dynamic/de/klassifikationen/ops/. [Accessed:
          <fpage>08</fpage>
          -May-2019]
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>European</given-names>
            <surname>Medicines</surname>
          </string-name>
          <string-name>
            <surname>Agency</surname>
          </string-name>
          , “
          <article-title>Introduction to ISO Identification of MedicinalProducts, SPOR programme</article-title>
          .”
          <fpage>26</fpage>
          -Nov-2016 [Online]. Available: https://www.ema.europa.eu/documents/other/introduction-iso
          <article-title>-identification-medicinal-products-sporprogramme_en</article-title>
          .pdf. [Accessed:
          <fpage>06</fpage>
          -May-2019]
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>European</given-names>
            <surname>Medicines</surname>
          </string-name>
          <string-name>
            <surname>Agency</surname>
          </string-name>
          ,
          <article-title>“Data on medicines (ISO IDMP standards): Overview</article-title>
          ,”
          <year>2019</year>
          [Online]. Available: https://www.ema.europa.eu/en/human
          <article-title>-regulatory/overview/data-medicines-iso-idmpstandards-overview</article-title>
          . [Accessed:
          <fpage>08</fpage>
          -May-2019]
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>European</given-names>
            <surname>Medicines</surname>
          </string-name>
          <string-name>
            <given-names>Agency</given-names>
            , “Substance &amp;
            <surname>Product Management Services (P&amp;SMS) update</surname>
          </string-name>
          ,
          <source>P&amp;SMS SG workshop &amp; SPOR Task Force meetings 19-22 June</source>
          <year>2018</year>
          .”
          <fpage>19</fpage>
          -Jun-2018 [Online]. Available: https://www.ema.europa.eu/documents/presentation/presentation-substance
          <article-title>-product-managementservices-psms-update_en</article-title>
          .pdf. [Accessed:
          <fpage>09</fpage>
          -May-2019]
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>European</given-names>
            <surname>Medicines</surname>
          </string-name>
          <string-name>
            <surname>Agency</surname>
          </string-name>
          , “
          <article-title>Referentials Management Service (RMS)</article-title>
          .
          <article-title>” 2019 [Online]</article-title>
          . Available: https://www.ema.europa.eu/en/human
          <article-title>-regulatory/research-development/data-medicines-iso-idmpstandards/spor-master-data/referentials-management-service-rms</article-title>
          . [Accessed:
          <fpage>09</fpage>
          -May-2019]
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <article-title>“Substance, product, organisation and referential (SPOR) master data</article-title>
          .” [Online]. Available: https://www.ema.europa.eu/en/human
          <article-title>-regulatory/research-development/data-medicines-iso-idmpstandards/substance-product-organisation-referential-spor-master-data</article-title>
          . [Accessed:
          <fpage>08</fpage>
          -May-2019]
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>European</given-names>
            <surname>Medicines</surname>
          </string-name>
          <string-name>
            <surname>Agency</surname>
          </string-name>
          , “
          <article-title>Substance and product data management services</article-title>
          .”
          <year>2019</year>
          [Online]. Available: https://www.ema.europa.eu/en/human
          <article-title>-regulatory/research-development/data-medicines-isoidmp-standards/spor-master-data/substance-product-data-management-services</article-title>
          . [Accessed:
          <fpage>09</fpage>
          -
          <lpage>May2019</lpage>
          ]
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Zivkovic</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Su</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Lee</surname>
          </string-name>
          , and E. Bortnichak, “
          <article-title>A Systematic Review of Coding Systems Used in Pharmacoepidemiology</article-title>
          and Database Research,” Methods Inf. Med., vol.
          <volume>57</volume>
          , no.
          <issue>01</issue>
          /02, pp.
          <fpage>01</fpage>
          -
          <lpage>42</lpage>
          , Feb.
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13] World Health Organisation (WHO), “International Nonproprietary Names,”
          <year>2019</year>
          [Online]. Available: https://www.who.int/medicines/services/inn/en/. [Accessed:
          <fpage>09</fpage>
          -May-2019]
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>DIMDI</given-names>
            <surname>Deutsche</surname>
          </string-name>
          <article-title>Institut für Medizinische Dokumentation und Information, “Rohdaten der Stoffbezeichnungen</article-title>
          .”
          <year>2019</year>
          [Online]. Available: https://www.dimdi.de/dynamic/de/arzneimittel/arzneimittel-recherchieren/rohdaten stoffbezeichnungen/. [Accessed:
          <fpage>08</fpage>
          -May-2019]
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>K. A.</given-names>
            <surname>Hamill</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R. D.</given-names>
            <surname>Nelson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. G.</given-names>
            <surname>Vander Stouw</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R. E.</given-names>
            <surname>Stobaugh</surname>
          </string-name>
          , “
          <article-title>Chemical Abstracts Service Chemical Registry System</article-title>
          .
          <volume>10</volume>
          .
          <article-title>Registration of substances from pre-1965 indexes of Chemical Abstracts,”</article-title>
          <string-name>
            <given-names>J.</given-names>
            <surname>Chem</surname>
          </string-name>
          .
          <source>Inf. Comput. Sci.</source>
          , vol.
          <volume>28</volume>
          , no.
          <issue>4</issue>
          , pp.
          <fpage>175</fpage>
          -
          <lpage>179</lpage>
          , Nov.
          <year>1988</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>US</given-names>
            <surname>Food</surname>
          </string-name>
          and
          <article-title>Drug Administration (FDA), “Substance Registration System - Unique Ingredient Identifier (UNII)</article-title>
          .
          <article-title>” 2019 [Online]</article-title>
          . Available: https://fdasis.nlm.nih.gov/srs/srs.jsp. [Accessed:
          <fpage>08</fpage>
          -
          <lpage>May2019</lpage>
          ]
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>