<!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>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Kalinka Kaloyanova</string-name>
          <email>kkaloyanova@fmi.uni-so</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ina Naydenova</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Zlatinka Kovacheva</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Faculty of Mathematics and Informatics, Sofia University St.Kliment Ohridski 5 James Bourchier blvd.</institution>
          ,
          <addr-line>1164, Sofia</addr-line>
          ,
          <country country="BG">Bulgaria</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Institute of Mathematics and Informatics, Bulgarian Academy of Sciences</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University of Mining and Geology „St. Ivan Rilski“</institution>
        </aff>
      </contrib-group>
      <fpage>155</fpage>
      <lpage>164</lpage>
      <abstract>
        <p>Data quality is an important part of information processing, but its application in practice is often underestimated. The complexity of data quality management, especially in the case of big data, makes it difficult to work in different areas of application. Although medical records are a significant source of errors in most cases data quality assessment on medical data is partially performed. The presented data quality analysis and recommendations in this paper can help physicians and software developers to understand better data quality dimensions, identify gaps in quality assessment, and develop |own procedures and techniques that correspond to their specific use cases.</p>
      </abstract>
      <kwd-group>
        <kwd>Data Quality</kwd>
        <kwd>Data Quality Dimensions</kwd>
        <kwd>Healthcare</kwd>
        <kwd>Medical Records</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>The use of software applications in healthcare is growing constantly. Data stored
in various information systems help medical workers to provide efficient treatment
of their patients every day. Moreover, this data can also be used for statistics,
analysis, prognoses. The secondary use of clinical data has been established in
recent years as a promising direction for data analysis and decision-making in
healthcare. It can be used to optimize the workflow in hospitals and other medical
centers.</p>
      <p>The quality of clinical data has not only an immediate impact on operative
medical processes but also a long-term influence on the research of accumulated
and aggregated clinical data. Inconsistency in data, missing values, invalid data –
all forms of uncertain or inaccurate data, questions the usefulness of the collected
data. Ignoring data quality issues leads to the worthlessness of data collection
efforts because no value is created.</p>
      <p>Big data raises new issues in data management at all, including the data
quality processes. New dimensions of data quality should be addressed, to
overcome these challenges of the huge amount of data coming from different sources,
stored in different ways (structured and unstructured data), the speed of data
generation and how to handle it in a timely manner.</p>
      <p>In this paper we discuss important aspects of data quality, refer to the
common data quality dimensions and analyze their application in the healthcare
domain. Finally, we present a set of guidelines for the implementation of a
successful data quality process.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Common data quality dimensions</title>
      <p>
        First researches on data quality appeared in 1990 and different definitions
were proposed during the years. Later, the main principles of data quality were
described in the standard ISO/TS 8000-1:2011 [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. ISO/IEC 25000:2014 defines
data quality as “degree to which the characteristics of data satisfy stated and
implied needs when used under specified conditions”[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>
        To understand data quality, different data quality dimensions should be
considered. Dimensions represent measurable data quality characteristics. Some of these
dimensions are related to the particular domain, users, or services. ISO/IEC 25012
focuses on Data Quality Model and classifies 15 data quality characteristics into
two groups: Inherent Data Quality and System Dependent Data Quality [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. The
group of inherent characteristics presents dimensions that are relevant in most cases
such as accuracy, completeness, and consistency, currentness (timeliness):
• Accuracy – presents the degree to which attributes of data correctly
represent the true value of the characteristics of the intended object. Accuracy
can be seen as syntactic as well as semantic accuracy.
• Completeness – measures the degree to which an entity has values for all
attributes that are expected.
• Consistency – the degree to which data attributes have no conflict and are
consistent with other data (and their attributes).
• Currentness – reflects how sufficiently up-to-day are data attributes in the
specific context of use.
      </p>
      <p>
        Accessibility, creditability, compliance, efficiency, and confidentiality
complement this group. The other group – System Dependent Data Quality group
consists of dimensions, that reflect the degree to which the quality of data in a
computer system is achieved and maintained when the data is used under certain
conditions. This includes availability, recoverability, portability, as well as
precision, traceability, and understandability [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>
        Wang in [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] and [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ] commenced in-depth research on data quality and its
dimensions more than twenty years ago. Further, many researchers discuss data
quality problems and characteristics [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. A survey, presented in [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]
observes a variety of sources and discusses data quality dimensions and identifies
the most frequently cited of them. It also concerns poor data classification issues.
      </p>
      <p>
        Recently, data quality understanding evolves in the case of Big data [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
Not only the enormous volumes of data are the challenge, but also the diversity of
their sources and applications domains – documents, images, audio, video, maps,
linked open data, social media, sensor data [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. So a new dimension trust that
reflects the reputation and reliability of the source is also considered [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Data types
also vary and the part of unstructured data and semi-structured data is growing
more and more than the structured ones.
      </p>
      <p>
        Rapid changes in data values raise the question of their timeliness, which is
too short in many cases. This, in connection to data veracity, raises the question
of the objectivity of the data and therefore of the analyses that are made on them.
The validity of data should be at the highest level, too, in order to bring a business
value [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Data quality challenges in the eHealth area</title>
      <p>
        Despite common problems with data quality, specific domains also influence
quality dimensions. Health information is used to aim medical decisions for
primary patient care and to support the continuity of treatment between different
medical providers [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. It is crucial for these decisions to be made on the basis of
complete and reliable data.
      </p>
      <p>Medical data provide knowledge about individual patients or groups of
patients – facts about their health condition that are subject to further processing.
These are mostly textual data and numeric values but also can include images,
audio, and even video data.</p>
      <p>
        Individual data present the health characteristics of individual patients, most
often in the context of a disease. Both, structured and unstructured data are used.
Data quality dimensions accuracy, completeness, correctness are of great
importance here. In many cases, free text data fields are used in primary care software
systems that do not require all needed information to be entered and enable this
information to be presented in a non-consistent way. There are cases where some
data fields in medical records stay empty as the requested information is not
entered or is not yet known. As doctors have to balance between patient care and
data entering, the information side is not the priority. Measurement errors,
recording errors, or transcription mistakes are often seen [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Other errors arise when
documents are transferred between different systems.
      </p>
      <p>
        An essential aspect of medical data is its confidentiality – who are the
authorized persons that have access to the particular piece of information and in which
cases they could use it [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>In addition to the primary use of health information, the obtained data can be
summarized and further processed to serve for more in-depth research, statistics,
trends detection. In the case of secondary use of clinical data, the volatility
dimension, which reflects how quickly data is changed, becomes important. Invalid
or inaccurate data also may influence the obtained conclusion. Other quality
dimensions such as usability, usefulness, and relevance complement the main set
of data quality characteristics accuracy, validity, completeness, and currentness.</p>
      <p>
        Using standards is a common way to overcome many issues in data
processing. Health Level 7 (HL7), ISO/IEC 13606, Systematized Nomenclature of
Medicine (SNOMED), Digital Imaging and Communications in Medicine (DICOM)
have been established as basic international standards for health data processing
[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. But their implementation at all levels of data processing is not yet
widespread. Semantic interoperability is still a challenge for software applications
presenting medical data in most countries. Other standards in connection with
data presentation in software systems are noted in [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. The use of medical
devices sending streaming information poses other challenges inherent in Big
data [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. Even the use of the appropriate standards is not able to guarantee full
prevention from data errors because they evolve constantly [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
      </p>
      <p>
        Data codification is another approach to overcome the incompatibility of
data and to achieve unification. Тhe International Classification of Diseases
(ICD) goes through several versions to reach ICD-11 revision. The Anatomical
Therapeutic Chemical (ATC) classification system classifies the active
ingredients of drugs and it is used as a pharmaceutical coding system [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
4
      </p>
    </sec>
    <sec id="sec-4">
      <title>Motivation case study</title>
      <p>Various computer applications operate in Bulgarian healthcare. They generate
a significant amount of data. Medical data is often presented in XML format.
In Bulgarian healthcare, the National Health Insurance Fund (NHIF) also uses
this approach. A set of predefined XSD schemes provides various templates for
different medical providers in the country in order to achieve regular information
about their activities to NHIF. The templates consist of predefined data fields
presenting common information about doctors and medical practice, patients’
personal information, as well as information about their medical condition and
treatment.</p>
      <p>
        As a motivation case study, we considered a multitude of samples obtained
from different software applications used by general practitioners, hospitals, and
several other medical centers in the country. All they present information in XML
format, following the XSD schemes, provided by the NHIF site for the particular
medical providers [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ].
      </p>
      <p>In addition to the administrative information for patients and medical
institutions, these records contain information about patients’ illnesses, medications
used, treatment periods, and other data, specific to medical provider and
application type.</p>
      <p>
        For example, the Outpatient card – one of the main documents, used by
general practitioners in Bulgarian healthcare, presents information about patients
visits. Every year more than 25 000 000 patients’ visits are recorded using this
template [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Some of the sections of this template allow free text entry and the
use of abbreviations and acronyms that significantly complicates understanding
and further processing of this information. In this way data accuracy, integrity
and completeness are not met or partially implemented.
      </p>
      <p>Information systems used in hospitals in the country also allow such free
data fields. We obtained and analyzed XML extracts with information about
thousands of patients of a hospital, many drug protocols, clinical procedures,
dispensary observations, etc. All personal data was anonymized. In the case of hospitals,
inconsistency in the date in and out of a patient in the hospital is a potential source
of erroneous data, as there exist different types of XML extracts for patients,
admitted to the hospital and the leaving ones. This additionally affects the data
consistency dimension.</p>
      <p>Possible conflicts of information could be found even in more structured
data fields, which are usually used for administrative information. For
example, when comparing gender field and information, extracted from patient EGN
(Personal identification number in Bulgaria). Mismatched numbers of medical
practices, branch numbering, and other demographic data fields with data out
of range.</p>
      <p>Further, medical data could be incorrectly recorded. For example, the results
of a laboratory test or blood pressure measurement may be partially or
completely wrong, which raises again accuracy and validity problems. Moreover,
there could be incompatibility on a logical level – between patient’s diagnosis
and prescribed medicine or between patient’s age and medical procedures or
prescribed medicine.</p>
      <p>Taking into account the number of medical records, produced from the
various systems, data usefulness should be considering be when data is collected.
This will reflect on the cost for assembling, storing, processing, and
dissemination of the information. The right balance between all dimensions will improve
the performance of all data management activities.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Guidelines for data quality process implementation</title>
      <p>A primary goal for establishing an efficient framework for data quality
management is to prevent data errors in collecting and storing data. Based on
the issues discussed above we outline a set of guidelines that could be used to
set up a framework for data quality prevention and management in Bulgarian
healthcare.</p>
      <sec id="sec-5-1">
        <title>5.1 Quality planning</title>
        <p>The first step for building a common framework for data quality management
requires a systematic way to cover all aspects concerning data quality. Data quality
planning will help organizations to maintain the balance between data quality goals
and resources needed to reach them. To be a successful one, it should include:
• Identifying all roles, involved in the data quality management process
First, these are medical workers – doctors, nurses, therapists, dentists,
pharmacists, etc., insurers, representative of administrative structures in healthcare at
a local and national level. Also, policymakers and lawmakers. Patients and their
relatives should be considered, too.</p>
        <p>• Identifying data to be collected</p>
        <p>All data sources should be identified, the user’s requirements about data –
collected and structured, and data formats – defined.</p>
        <p>• Determining data quality goals and dimensions</p>
        <p>The list of quality characteristics should be established following common
data quality dimensions and choosing additional dimensions that are most
appropriate to reach the goal of the particular case.</p>
        <p>• Choosing appropriate standards</p>
        <p>The set of used standards depends on data sources and data formats and the
goals and requirements for the system to be implemented.</p>
        <p>• Defining rules</p>
        <p>Different rules can be considered for incompatibility, incompleteness,
duplication of data. Other groups of rules can concern values out of range, temporal
sequence errors, data that is incompatible with other data.</p>
        <p>• Defining metrics</p>
        <p>The state of data can be measured based on standard metrics, applicable for
every particular data set. In addition, specific to the area and application context
business constraints could be defined.</p>
      </sec>
      <sec id="sec-5-2">
        <title>5.2 Quality assurance</title>
        <p>Besides standard recommendations for quality assurance, it will be useful as much
as possible data errors’ eventualities to be prevented through implementation in
the software applications. Below several suggestions for the development of
software systems in healthcare are listed:
• Applying data patterns:
− Use of standards;
− Use of archetypes;
− Use of international coding conventions.</p>
        <p>The application of specific to healthcare standards will facilitate data
processing. Previously defined archetypes can control values, that describe different
parameters of patient’ state. The implementation of the coding conventions like
IDC and ATC allow storing the codes into appropriate structures and choosing,
instead of entering values, which will prevent typing errors. It also supports the
semantic interoperability between different systems.</p>
        <p>• Standardization of data entering processes
− Use of appropriate user interface;
− Use of data entry templates;
− Validation of data entry fields.</p>
        <p>The use of common interface templates helps users to feel confident when
working with the system. User control and freedom should be provided
consistently through all system functions. The timely verification of the entered data will
avoid storing wrong data into data structures.</p>
        <p>• Implementing rules</p>
        <p>Software implementation of all rules, defined during Quality planning is an
efficient way to prevent data errors. Appropriate error messages should be
considered when rules are broken.</p>
        <p>• Checking data using software tools
− Providing data entering fields based on standards;
− Validation of the range of parameters;
− Checking diagnoses, and drug compatibility;
− Writing special application programs.</p>
        <p>All data should be validated on input. Recognition of data (using predefined
values, codes, archetypes, etc.) instead of direct data entering, will avoid entering
incorrect data.</p>
        <p>• Providing appropriate kinds of help, documentation, and training.</p>
        <p>In many cases training of different groups of users is recommended – for
example, administrative staff, clinical staff, etc. Well-structured documentation,
help pages, and other supporting documentation have proven their effectiveness.</p>
      </sec>
      <sec id="sec-5-3">
        <title>5.3 Quality control</title>
        <p>Data Quality Control follows all recommendations of the plans established during
Quality Planning. Data should be processed according to the specified rules,
following the prescribed procedures. Taking appropriate feedback, providing
regular quality reviews, will help to identify and appropriately react every time
when data processing does not meet data quality requirements.</p>
        <p>
          In order to provide a common language and a harmonized approach to
measuring and improving data quality in the eHealth area, the World Health
Organization in collaboration with other organizations proposes a Data Quality Review
(DQR) toolkit and methodology. It includes guidelines that promote framework
and institutionalization of regular and independent review and assessment of the
data quality state at different levels of the health system in countries (national,
district, and facility). Several tools that can be adapted by users are also included
[
          <xref ref-type="bibr" rid="ref19">19</xref>
          ].
        </p>
      </sec>
      <sec id="sec-5-4">
        <title>5.4 Quality improvement</title>
        <p>Considering the results coming from the data quality monitoring and control
activities (system assessment, data verification, help desk reviews, etc.) it is
reasonable for a working group on data quality to lead the development and
implementation of a data quality improvement plan. It is recommended, when
working on the plan to:
• outline the activities, that will address the problems, pointed out during
the assessment;
• allocate the resources;
• identify the staff, that will provide all procedures to improve the quality
of data.</p>
        <p>As for the list of the activities, first should be implemented these ones, which
will cause a major impact on overall data quality [20].
6</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Conclusions</title>
      <p>In this paper important characteristics of data quality were discussed and related
to data used in healthcare. The quality of data is essential to achieve the full
potential of healthcare data accumulated so far and the quality characteristics of
this data should match certain levels. We analyzed major data quality issues and
formulated a set of guidelines for data quality planning, assurance, and control
that could be successfully applied for the healthcare domain.</p>
      <p>All presented guidelines are subject to many extensions especially in terms
of their practical implementation. Considering the significant role of the specific
subject area, defining a data quality assessment model for medical data used in
Bulgarian healthcare is one of our next goals.
7</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgments</title>
      <p>This paper is supported by the project BG05M2OP001-1.001-0004 Universities
for Science, Informatics and Technologies in the e-Society (UNITe) and the
National Scientific Program “eHealth” in Bulgaria.
20. World Health Organization, 2020: Overview of the Data Quality Review (DQR) Framework
and Methodology,
https://cdn.who.int/media/docs/default-source/data-quality-pages/who-dqrframework-v1-0-overview.pdf?sfvrsn=280bb67_5&amp;sequence=1&amp;isAllowed=y, last accessed
2021/04/10.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Batini</surname>
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rula</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Scannapieco</surname>
            <given-names>M.</given-names>
          </string-name>
          , and Viscusi G.:
          <article-title>From Data Quality to Big Data Quality</article-title>
          .
          <source>J. Database Management</source>
          , vol
          <volume>26</volume>
          , no 1:
          <fpage>60</fpage>
          -
          <lpage>82</lpage>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Batini</surname>
            <given-names>C.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Scannapieco</surname>
            <given-names>M.</given-names>
          </string-name>
          :
          <source>Data and Information Quality</source>
          , Springer (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Cai</surname>
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhu</surname>
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>The Challenges of Data Quality and Data Quality Assessment in the Big Data Era Data Science Journal</article-title>
          ,
          <volume>14</volume>
          : 2, pp.
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Caballero</surname>
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Serrano</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Piattini</surname>
            <given-names>M.:</given-names>
          </string-name>
          <article-title>A Data Quality in Use Model for Big Data</article-title>
          .
          <source>In Advances in Conceptual Modeling. ER 2014. Lecture Notes in Computer Science</source>
          , vol.
          <volume>8823</volume>
          :
          <fpage>65</fpage>
          -
          <lpage>74</lpage>
          . Springer, Cham (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. ISO/TS 8000-1:
          <fpage>2011</fpage>
          ,
          <string-name>
            <surname>Data</surname>
          </string-name>
          quality - Part 1: Overview https://www.iso.org/standard/ 50798.html,
          <source>last accessed</source>
          <year>2021</year>
          /03/12.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6. ISO/IEC 25000:
          <year>2014</year>
          ,
          <article-title>Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) -</article-title>
          Guide to SQuaREISO/IEC, “
          <article-title>Software engineering - Software product Quality Requirements</article-title>
          , https://www.iso.org/obp/ ui/#iso:std:iso-iec:25000:ed-2
          <source>:v1:en, last accessed</source>
          <year>2021</year>
          /03/18.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <source>ISO/IEC 25012 Software and Data Quality</source>
          , https://iso25000.com/index.php/en/iso25000-standards/iso-25012, last accessed
          <year>2021</year>
          /03/18.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Kaloyanova</surname>
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krastev</surname>
            <given-names>E.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Mitreva</surname>
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>Extracting Data from General Practitioners' XML Reports in Bulgarian Healthcare to Comply with ISO/EN 13606</article-title>
          .
          <source>In: Proceedings of the 9th Balkan Conference on Informatics (BCI'19)</source>
          , Sofia, Bulgaria,
          <source>ACM DL, Article</source>
          <volume>3</volume>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Kim</surname>
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Data Quality in Healthcare - Challenges, Limitations &amp; Steps to Take for Quality Improvement</article-title>
          , https://dataladder.com
          <article-title>/data-quality-in-healthcare-data-systems</article-title>
          ,
          <source>last accessed</source>
          <year>2021</year>
          /03/12.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Krastev</surname>
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tcharaktchiev</surname>
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kirov</surname>
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kovatchev</surname>
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Abanos</surname>
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Lambova</surname>
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2019</year>
          )
          <article-title>Software Implementation of the EU Patient Summary with Archetype Concept</article-title>
          ,
          <source>In: Proceedings of GLOBAL HEALTH</source>
          <year>2019</year>
          , The Eighth International Conference on Global Health Challenges, Porto, Portugal,
          <source>September 22-26</source>
          , pp.
          <fpage>8</fpage>
          -
          <lpage>13</lpage>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Krastev</surname>
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tcharaktchiev</surname>
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kaloyanova</surname>
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kirov</surname>
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kovatchev</surname>
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Abanos</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mateva</surname>
            <given-names>N.</given-names>
          </string-name>
          (
          <year>2020</year>
          )
          <article-title>Standards Based Adaptation of Clinical Documents for Interoperability of e-Health Services</article-title>
          ,
          <source>In: Proceedings of the 13th Conference on Information Systems and Grid Technologies (ISGT</source>
          <year>2020</year>
          ), Sofia, Bulgaria, May
          <volume>29</volume>
          - 30,
          <year>2020</year>
          , CEUR-WS.org/Vol-
          <volume>2656</volume>
          /paper2.pdf,
          <source>last accessed</source>
          <year>2021</year>
          /03/17.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Laranjeiro</surname>
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Soydemir</surname>
            <given-names>S. N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bernardino</surname>
            <given-names>J.:</given-names>
          </string-name>
          <article-title>A Survey on Data Quality: Classifying Poor Data</article-title>
          ,
          <source>In: Proceedings of the IEEE 21st Pacific Rim International Symposium on Dependable Computing (PRDC)</source>
          , Zhangjiajie, China, pp.
          <fpage>179</fpage>
          -
          <lpage>188</lpage>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Mahn-DiNikola</surname>
            <given-names>V</given-names>
          </string-name>
          .:
          <article-title>Six Dimensions of Data Fitness</article-title>
          , https://blog.medisolv.com/articles/sixdimensions-of
          <article-title>-data-fitness</article-title>
          ,
          <source>last accessed</source>
          <year>2021</year>
          /03/31.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>NHIF</surname>
          </string-name>
          .
          <article-title>National Health Insurance Fund. “XML file format for submitting requests by doctors and specialists for accounting completed ambulatory activities in primary and specialized patient care after January 1st</article-title>
          .,
          <year>2021</year>
          ”, https://www.nhif.bg/page/28, last accessed
          <year>2021</year>
          /02/15.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Richardson</surname>
            <given-names>I.</given-names>
          </string-name>
          :
          <article-title>Healthcare Systems Quality: Development and Use</article-title>
          ,
          <source>In: Proceedings of the International Workshop on Software Engineering in Healthcare Systems</source>
          , Austin, USA, pp.
          <fpage>50</fpage>
          -
          <lpage>53</lpage>
          (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Ristevski</surname>
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Savoska</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Blazheska-Tabakovska N</surname>
          </string-name>
          .:
          <article-title>Opportunities for Big Data Analytics in Healthcare Information Systems Development for Decision Support</article-title>
          ,
          <source>In: Proceedings of the 13th Conference on Information Systems and Grid Technologies (ISGT</source>
          <year>2020</year>
          ), Sofia, Bulgaria,
          <year>2020</year>
          , CEUR-WS.org/Vol-
          <volume>2656</volume>
          /paper4.pdf,
          <source>last accessed</source>
          <year>2021</year>
          /03/12.
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Wang R. Y</surname>
          </string-name>
          . and
          <string-name>
            <surname>Strong D. M.</surname>
          </string-name>
          <article-title>: Beyond accuracy: What data quality means to data consumers</article-title>
          ,
          <source>Journal of Management Information Systems</source>
          , Vol.
          <volume>12</volume>
          , no.
          <issue>4</issue>
          :
          <fpage>5</fpage>
          -
          <lpage>33</lpage>
          (
          <year>1996</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Wang</surname>
          </string-name>
          , R.Y.:
          <article-title>A product perspective on total data quality management</article-title>
          ,
          <source>Communication of ACM</source>
          Vol
          <volume>41</volume>
          , no 2:
          <fpage>58</fpage>
          -
          <lpage>65</lpage>
          (
          <year>1998</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19. World Health Organization,
          <year>2017</year>
          :
          <article-title>Data quality review: Module 1: framework and metrics</article-title>
          ,
          <source>ISBN</source>
          <volume>9789241512725</volume>
          , https://apps.who.int/iris/handle/10665/259224, last accessed
          <year>2021</year>
          /04/10.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>