<!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>
      <journal-title-group>
        <journal-title>June</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Evaluating Clinical-Care Metadata Share and its FAIRification using the REA Ontology⋆</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Syeda A. Sohail</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Faiza A. Bukhsh</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Maurice van Keulen</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Johannes G. Krabbe</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Pavel Hruby</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Medische Spectrum Twente</institution>
          ,
          <addr-line>Medlon BV, 7500 KA Enschede</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>REA Technology</institution>
          ,
          <addr-line>Copenhagen</addr-line>
          ,
          <country country="DK">Denmark</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University of Twente</institution>
          ,
          <addr-line>Drienerlolaan 5, Enschede</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2022</year>
      </pub-date>
      <volume>0</volume>
      <fpage>6</fpage>
      <lpage>10</lpage>
      <abstract>
        <p>The FAIRification of data facilitates a fast-paced, global, FAIR metadata availability across domains for the sustainable growth of public/private organizations. Likewise, in healthcare, the clinical labs aim to achieve FAIR (biosample) metadata by keeping patient-specific infectious disease records. However, the responsible evaluation of the FAIRification process of Dutch clinical lab metadata is lacking at the local and global levels. From a responsible data science perspective, we normatively (in-principle) and empirically (in-practice) evaluate the Dutch clinical lab metadata share against FACT principles. The normative evaluation involved content analysis of FAIR concerning peer-reviewed publications and oficial websites. The empirical evaluation comprised a documentation review of standardized (public/confidential) documents regarding the metadata share of Dutch clinical labs. The evaluations assisted us in formulating two REA models based on REA ontology. The first REA model depicts the clinical lab metadata production run at a local/national level. The second REA model specifies the work (flow) breakdown structure of global FAIRification for FHIR Netherland using linkage relationship against FACT principles. In-field (IT and REA ontology) experts further evaluated the REA models for functional and structural veracity. Furthermore, our evaluations verified the presence of an underlying privacy-utility tradeof in FAIRification of clinical lab metadata where data utility is prioritized over data protection.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;FAIRification</kwd>
        <kwd>REA ontology</kwd>
        <kwd>FACT principles</kwd>
        <kwd>Dutch clinical-care</kwd>
        <kwd>Responsible Data Science</kwd>
        <kwd>Data protection</kwd>
        <kwd>Data Utility</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        The recent intensified FAIRification eforts stem from including global FAIR data repositories,
as an ultimate goal, by pan-European and national public authorities [
        <xref ref-type="bibr" rid="ref1 ref2 ref3">1, 2, 3</xref>
        ]. FAIRification is
the process of making metadata FAIR, i.e., Findable, Accessible, Interoperable, and Reusable
[
        <xref ref-type="bibr" rid="ref3 ref4 ref5">4, 5, 3</xref>
        ]. A similar FAIR data drive seeks an all-rounded, concerted technological, organizational,
and strategic efort in the healthcare domain [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. In this wake, GDPR (recital 53) obligates
the member states for harmonized conditions to ensure sustainable national/central and
cross-border healthcare services and systems [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Furthermore, for optimal data utility, GDPR
(recital 5) ordains uninterrupted personal data share amongst public and private actors (i.e.,
both natural persons and organizations) [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. The measures mentioned above are an extension
of the GDPR objective of achieving free movement of personal data within the EU [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] and
align with the FAIRification process [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ]. Therefore, an ethical evaluation of the FAIRification
process of Dutch healthcare metadata share is required from a responsible data science (RDS)
perspective [
        <xref ref-type="bibr" rid="ref10 ref11">10, 11</xref>
        ]. In this wake, an evaluation against FACT principles (of RDS) aims for fair,
accurate, confidential, and transparent data handling from healthcare providers’ viewpoint
[
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] and seek both: data utility and data protection [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. Thus, the FACT principles seem
applicable to the healthcare domain in efectively dealing with the dilemma of Privacy Utility
Tradeof (PUT), where the precision of data analytics (i.e., data utility) is as crucial as the
privacy-preservation of data subjects (i.e., data protection) [
        <xref ref-type="bibr" rid="ref13 ref14 ref15 ref16">13, 14, 15, 16</xref>
        ].
      </p>
      <p>
        Contribution; Using Value Modeling and the REA Ontology: Why Value Modeling? During the
last three decades, the pan-European and local regulations [
        <xref ref-type="bibr" rid="ref17 ref18 ref19">17, 18, 19</xref>
        ] gradually standardized
the care services (events), the performing agents, and (metadata) resource requirements.
Standardized metadata trace of patients’ value care relies upon the uninterrupted (data-utility
prone) care-metadata share amongst Dutch healthcare givers [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. Data utility is the precision
of (meta) data analytics, whereas data protection aims at privacy preservation of data subjects
[
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. The former is an integral part of the FAIRification process [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], whereas FACT principles of
RDS encompass both [
        <xref ref-type="bibr" rid="ref10 ref11">11, 10</xref>
        ]. Why the REA Ontology? Previously, we conceptualized the Dutch
care metadata share landscape from a patient’s perspective using REA ontology to highlight:
the vital economic agents, their prime interactions, and collective economic value gain or loss
[
        <xref ref-type="bibr" rid="ref14 ref15">15, 14</xref>
        ]. Here, the REA ontology identified the underlying financial factors and signified: who,
how, and what leads to the FAIRification of Dutch clinical lab metadata at a local production
run level to the global work (flow) breakdown structure level of FHIR Netherlands against
FACT principles of RDS [
        <xref ref-type="bibr" rid="ref10 ref11">10, 11</xref>
        ]. The objectives of the research work are twofold. The first is
to evaluate the (dual-level) FAIRification of Dutch clinical lab metadata against FACT principles
of RDS. Secondly, to specify the findings by formulating the REA (Resource, Event, Agent)
models and evaluating their functional and structural authenticity using expert opinion. To
attain the objectives, we followed the approach mentioned under the data analytical approach
in Section 3. The efectiveness of the selected approach relied upon following three factors.
Firstly, upon the successful mapping of FACT principles on labs’ (dual-level) metadata share
(see FACT-mapping determinants in Section 4). Secondly, upon the simplified specification of
(otherwise) complex, Dutch healthcare metadata share landscape using REA ontology. Thirdly,
upon the structural and functional evaluation of REA models using expert opinion.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        Clinical FAIR data was reportedly first required for the timely treatment of rare diseases (5 out
of 10,000) [20]. Later FAIRfication became a challenge across (research) domains to collectively
overcome the hurdles [21] to reap countless socio-economic benefits [
        <xref ref-type="bibr" rid="ref4">22, 4</xref>
        ]. FACT principles
were first highlighted as a concerted efort by Dutch scientists across Dutch universities for
responsible data science [
        <xref ref-type="bibr" rid="ref10 ref11">11, 10</xref>
        ]. The interlink between FAIR and FACT principles was first
reported in the field of crystallography [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. Since 2018, with the implementation of GDPR
[
        <xref ref-type="bibr" rid="ref7 ref8 ref9">9, 7, 8</xref>
        ], academia and industry have shown a bent toward the FAIRification of metadata across
domains. For example, the Dutch healthcare enterprises [23, 24], governments bodies [
        <xref ref-type="bibr" rid="ref2">25, 2</xref>
        ],
research and funding organizations [26] oficially set the FAIRification process as a business
goal. Data (pipeline) provenance amongst healthcare providers is maintained to attain data
utility. For example, locally, the hub and spoke model [27, 28] and globally, the FAIRification
of care metadata [
        <xref ref-type="bibr" rid="ref2">2, 23</xref>
        ] help assure data precision and transparency. On the other hand, data
protection is achievable with fair and confidential data handling [ 29, 30] secured by: design,
policy, and patients’ informed consent [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. The terms ’fair and confidential’ have multifaceted
social connotations and seek multi-dimensional means for their implications. Fair literally
means ’equal treatment,’ but the term has ethical implications in the healthcare domain and
seeks just, benevolent and non-maleficent measures at each step of patient’s value care and
implies service-dominant logic [31, 32]. Confidentiality entails doing research while keeping the
secrets of data subjects. Confidentiality partially covers privacy-preservation [ 33] and is partly
ensured with technical and organizational measures for data protection [34]. Privacy seeks
protection of an individual’s autonomy and direct/indirect control over personal information
share [35]. Both Fair and Confidential data predominantly depend upon privacy preservation,
and patients’ well-informed consent [36].
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Data Analytical Approach</title>
      <p>
        The Dutch clinical lab metadata share process is normatively (should-be state/ policy
specification) and empirically (as-is state/operationalization) evaluated against FACT principles of
RDS at local and global levels see Fig. 1. Normative evaluation includes a content analysis
using peer-reviewed publications and oficial websites of the FAIRification process by mapping
FACT principles. The empirical evaluation comprised the documentation review of standardized
public/confidential documents for labs’ metadata FAIRification using FACT mapping
determinants. The FACT mapping [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] determinants highlighted the metadata share bend either
towards data utility or data protection. Based on our evaluations, we formulated two REA
models [37]. The First REA model identified the production run of patients’ EHR (Electronic
Health Record) by highlighting key economic agents, their increment, and decrement events
using conversion duality for the clinical metadata as an economic resource. The second REA
model identified FHIR, FAIR Healthcare Information Repository, Netherlands work breakdown
structure vis-a-vis FACT (fair, accurate, confidential, transparent) principles. The REA models
were further verified by (in-field) IT and REA ontology experts concerning the functionality
and structural underpinnings of the REA models. For clarity see Fig. 1.
      </p>
    </sec>
    <sec id="sec-4">
      <title>4. REA Ontologies and Conceptual Verification using Clinical</title>
    </sec>
    <sec id="sec-5">
      <title>Labs as a Use Case</title>
      <p>The below given REA models follow the foundational fundamentals by [37].</p>
      <sec id="sec-5-1">
        <title>4.1. REA Model for Clinical Lab (Meta) Data Share at the Local/National Level</title>
        <p>This REA model (see Fig. 2) exhibits the lab metadata production run [37]. Here, economic
agents are a mixture of people and machines in locally sharing lab metadata as an economic
resource. The applicant, i.e., the patient or the concerned healthcare giver (GP, a specialist from
the hospital, or another lab), initiates the process with a (bio) sample request message as per
standardized communication protocol as an increment. Then, the lab undergoes decrement
events with the patient’s sample intake. The sampler collects the patient’s (bio) sample with a
separate (unique identifier) UID. The lab transports the sample tubes to the lab analyzer/source.
The analyzer with a UID is (mostly) an automatically functioning machine that conducts the
24/7 tests based on the tubes’ barcodes and authorizes sample results with a UID in the lab
information system. The analyzer utilizes rule-based ML algorithms. Afterward, the executor
does metadata formation of lab results, allows re-identification (i.e., versioning), and attaches
«Economic</p>
        <p>Agent»
Patients
«receives»
«provides»
«Economic Resource»</p>
        <p>Message as per
Communication</p>
        <p>Protocol
«Economic Resource»</p>
        <p>Bio Sample with</p>
        <p>Unique ID (UID)
«Economic Resource»
Source/Analyzer UID
with Sample result
«Economic Resource»</p>
        <p>Digital result with</p>
        <p>UID
«Economic Resource»
Patient file with UID</p>
        <p>Lab to lab
«Economic Agent»</p>
        <p>(Clinical) Lab
«provides»</p>
        <p>«provides»
«provides»
«receives»</p>
        <p>«provides»
«use»
«consumes»
«use»
«consumes»
«consumes»
«comitted
provide»
«comitted
provide»
«Decrement Event»
Sample diagnostic</p>
        <p>request
«Decrement Event»</p>
        <p>Sample intake
«Decrement Event»</p>
        <p>Sample analysis
«Decrement Event»</p>
        <p>Data versioning,
indexing and sending</p>
        <p>of results
«Decrement Event»</p>
        <p>Digital results to
applicant
«Economic Agent»</p>
        <p>GPs, specialists
(Hospital), pharmacy
«Economic Agent»</p>
        <p>Govt research
organizations
(RIVM), TTP
«receives»</p>
        <p>«receives»
«Increment Event»</p>
        <p>Lab results
reception
«Economic</p>
        <p>Resource»</p>
        <p>Digital Patients' Files
«produces»
«conversion
duality»
«comitted
provide»
«comitted
provide&gt;&gt;
«comitted
provide»
«grouping»
«Group»
Patients' EHR
«Economic Agent»</p>
        <p>Lab Applicant
«Economic Agent»</p>
        <p>Lab Sampler
«Economic Agent»</p>
        <p>Lab Analyzer
«Economic Agent»</p>
        <p>Lab Executer
results to the patient’s file (i.e., indexing), respectively. The lab executer is also (mostly) an
automatically functioning machine that sends a digital patient file with the lab results to the
applicant’s Electronic Health Record, EHR (i.e., a group [38]). The relationship "produces" can
be further modeled as an REA conversion process, and we omitted the details of this process for
simplicity.</p>
        <p>FACT mapping determinants allowed mapping of FACT principles on Dutch clinical lab
metadata share environment. We located the following determinants for each FACT indicator in
FAIRification concerning public/confidential documents, oficial websites, and peer-reviewed
scientific publications: for fairness: patient’s right over explicit Informed Consent, data
erasure/editing, data purpose, storage, and time limitations via authorities. For accuracy:
provenance maintaining measures for data pipeline such as UIDs usage for precise data entry. For
confidentiality: patients’ sensitive information-share protection by utilizing technical,
organizational, and data-oriented means. For transparency: measures to ensure re-identification
of accurately published data. In FACT principles, accuracy and transparency ensure the data
utility (precision of data analytics). At the same time, fairness and confidentiality ascertain
patients’ data protection concerning privacy (i.e., patient’s autonomous decision making
concerning personal information-share) preservation. FACT principles allowed us to identify the
FAIRification bend towards either data utility or data protection.</p>
        <p>Discussion and Evaluation: The below-given insights convey the crux of clinical labs’
(dual-level) metadata share evaluation. The insights highlight the areas where the FAIRification
process is compared against FACT principles of RDS and show a bend towards data utility at
the expense of data protection.</p>
        <p>
          Insight 1, Clinical labs’ data collection and metadata formulation prepare for later FAIRification :
Locally, the FAIRification by design, policy, and training, corresponds with the global level go
build, go change and go train [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] measures that are in place to attain FAIRification as a business
goal [
          <xref ref-type="bibr" rid="ref1 ref6">6, 39, 1, 26</xref>
          ]. FAIRifcation by design includes standardized IS architecture, (metadata
concerning) semantic models, syntax for language consistency using global UIDs for re-identification,
and technical interoperability assistance by ForeCare [40]. FAIRification by policy ascertains
[41, 42? ] an uninterrupted, transparent exchange of care metadata across stakeholders via
local/global standardizing, licensing, and oversight organizations[43]. Moreover, clinical labs
share completely unmasked data with the country-wide (public) care data repository ([25]) for
infectious diseases, renal diseases, antibiotic treatments, and scans. Additionally, via a national
cyber-lab, the lab tests are shared with pharmacies in real-time [44, 45]. FAIRification by training
facilitates healthcare providers’ with FAIRification trainings [ 46, 26, 47, 48, 49] as per set (global)
standards[42? ].
        </p>
        <p>
          Insight 2, Fully automated clinical labs, with automated IS and equipment, ensure transparent,
accurate metadata but raise ethical concerns [50]. Specifically, the (presumed) machine-based
decision-making algorithms for the labs’ (executer) functionality in a fully automatic Lab
Information System is ethically concerning [51]. Insight 3, Partial fairness and confidentiality
lead to privacy-lapse: The technical data security measures and access governance controls
are fully in place [52]. Still, privacy lapse is evident as patients’ autonomous decision-making
regarding personal information-share, their right to erasure/editing, knowledge for long/short
term storage, and time are disregarded in an opt-out IC intake. Therefore, an explicit, well
Informed Consent (IC) is less fully-practiced nationally[
          <xref ref-type="bibr" rid="ref17">53, 17, 42</xref>
          ].
        </p>
      </sec>
      <sec id="sec-5-2">
        <title>4.2. REA Model for Workflow Breakdown Structure of FHIR Netherlands and</title>
      </sec>
      <sec id="sec-5-3">
        <title>FACT Mapping Derterminants</title>
        <p>
          This REA model (see Fig. 3) is not an extension of the first REA model. Instead, separately
emphasizes the FAIRification workflow [
          <xref ref-type="bibr" rid="ref2">54, 2</xref>
          ] of FHIR (Fast Healthcare Interoperability Resources)
Netherlands [24] vis-à -vis FACT (fair, accuracy, confidentiality, transparency) principles [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ].
The FACT principles ensure responsible data science, whereas the FHIR NL comprises the
FAIRification procedural steps for better data utility. FAIRification value chain comprises
data reuse, curation, validation, de- identification, semantic model implication, data linkage,
licensing, versioning, data indexing, publishing, and metadata formation [54] and starts from
reusable stored clinical care data for research/clinical purposes. For clarity and concision, the
FAIRIfication steps [ 54] vis-a-vis FACT mapping determinants are condensed into 2-3 steps
in the top three boxes using linkage types [37]. In the top three right boxes, the ‘quantity
required’ are the steps required for FHIR Netherlands [41, 43, 42, 24, 55]. The dark color of
these boxes emphasizes their (active) operationalization in practice. Contrarily, the left top
three boxes are light-colored because the FACT principles are (oficially) ordained but partially
applied by downplaying fair and confidential data requirements. Finally, the top 3 (grey-colored)
middleboxes specify the operationalized/practiced economic resource types that ultimately
produce the economic resource of FAIR data for FHIR NL in the bottom-most (middle) boxes.
Similarly, in the bottom left box, the ‘quantity used’ is of FACT metadata which is accurate and
transparent but marginally fair and confidential.
        </p>
        <p>Discussion and Evaluation: Insight 4, Marginal fairness and confidentiality : The gradual
compromise on fair and confidential data is perceivable across the left boxes under quantity
required Fig. 3 for FACT principles. Because, in addition to an implicit, marginal IC intake,
patients’ de-identification is substituted with pseudonymization that allows later unmasking
personal information with a key. Moreover, globally, the standardized licensing, oversight and
regulatory authorities for FAIR data do the data publishing, data validating, and data versioning
that further reduces data protection [49]. Insight 5, grey areas concerning data-ownership of giant
healthcare enterprises: If labs are located within a Dutch hospital’s premises, the metadata
ownership rights rest unclear. The data transfer agreements with hospitals and GPs, ambiguously
bridge the gap. Some out-patient Dutch clinical labs [56] are not FHIR NL members. Still, as
almost all Dutch hospitals are members of FHIR NL, the former are PRESUMABLY sharing labs’
clinical data via the hospital’s EHR. Insight 6, Deliberative decision-making and alignment of
normative pledges and their operationalization: There is a dire need to bridge the strategic gap
between the EU policymakers, lawmakers, over-sight bodies, and the healthcare providers to
align the operationalization of clinical care metadata share with the oficial public/confidential
documents’ specifications. This is only possible with the inclusion of domain-specific industry
personnel into the policymaking, law-making, and oversight authorities as advisors.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>5. Conclusion</title>
      <p>
        We performed the evaluation of the Dutch clinical labs’ (dual-level) metadata share against
FACT principles of RDS. Based on the findings, we formulated two REA models that simplified
the otherwise complex Dutch care metadata share landscape. The (local) production run level
evaluation exhibited that the labs’ metadata formulation, processing, and storing take place
as per legal standards [57, 58, 59, 52] in preparation for the global FAIRification process. The
FACT mapping determinants identified that the provenance of the data pipeline using UIDs
ascertains the precision of data analytics (i.e., data utility) and transparency concerning patients’
value care. However, labs’ metadata as an economic resource is partially fair/just because of
the lack of patients’ explicit Informed Consent’s intake by labs. Patients’ confidentiality is also
partially ensured because the clinical labs share unmasked data with a country-wide (public)
data repository for infectious and renal diseases, antibiotic treatments, and scans. Additionally,
fully automatically interacting clinical labs with automated equipment and ISs raise ethical
concerns (regarding patients’ confidentiality and fairness). The first REA model specified the
economic agents interacting via events to perform the conversion duality of patients’ metadata
as an economic resource. The FACT mapping determinants demonstrate the bend towards data
utility over data protection. The second REA model, specifying the work (flow) breakdown
structure of FHIR NL vis-a-vis FACT mapping determinants, identifies the linkage relationship
for the quantity required for each resource type (i.e., functional step). In addition, the (linkage)
quantity used for the FAIR metadata in the bottom-most boxes specifies that the patients’ (actual)
metadata share contradicts the policy specifications in oficial public/confidential documents.
The contradiction occurs because, with each workflow step, the FAIR data is kept: accurate and
transparent but marginally fair and confidential to prioritize data utility. The research work
specified and evaluated the presence of Privacy Utility Tradeof (PUT) in the Dutch clinical labs’
(dual-level) metadata share as an extension of our ongoing research [
        <xref ref-type="bibr" rid="ref13 ref14 ref15 ref16">13, 14, 15, 16</xref>
        ]. In future
work, based on a more detailed local production run model, we aim to produce a mimic dataset
for PUT concerning process evaluation, including possible solutions.
[20] J. Schaaf, D. Kadioglu, J. Goebel, C.-A. Behrendt, M. Roos, D. van Enckevort, F. Ückert,
F. Sadiku, T. O. Wagner, H. Storf, Osse goes fair–implementation of the fair data principles
for an open-source registry for rare diseases, in: German Medical Data Sciences: A
Learning Healthcare System, IOS Press, 2018, pp. 209–213.
[21] R. D. Kush, D. Warzel, M. A. Kush, A. Sherman, E. A. Navarro, R. Fitzmartin, F. Pétavy,
J. Galvez, L. B. Becnel, F. Zhou, et al., Fair data sharing: the roles of common data elements
and harmonization, Journal of Biomedical Informatics 107 (2020) 103421.
[22] C. Labadie, C. Legner, M. Eurich, M. Fadler, Fair enough? enhancing the usage of enterprise
data with data catalogs, in: 2020 IEEE 22nd Conference on Business Informatics (CBI),
volume 1, IEEE, 2020, pp. 201–210.
[23] BBMRI, Biobanking netherlands, 2017. URL: https://www.bbmri.nl/.
[24] FHIRnl, Fhir: Standard for health care data share, by hl7, 2017. URL: http://www.hl7.org/
hfir/.
[25] RIVM, National institute for health and environment, 2017. URL: https://www.rivm.nl/.
[26] ZONMWnl, Reserach funding for fair data and data management, 2022. URL: https://www.
      </p>
      <p>zonmw.nl/nl/over-zonmw/open-science/fair-data-en-datamanagement/.
[27] P. Joseph, Eliminating disparities and implicit bias in health care delivery by utilizing a
hub-and-spoke model, Research Ideas and Outcomes 4 (2018) e26370.
[28] D. James, D. Truman, Improvement in laboratory test turnaround times for inpatients
following move to hub and spoke model of delivery, Practical Laboratory Medicine 1
(2015) 2–4.
[29] M. Boeckhout, G. A. Zielhuis, A. L. Bredenoord, The fair guiding principles for data
stewardship: fair enough?, European journal of human genetics 26 (2018) 931–936.
[30] A. Landi, M. Thompson, V. Giannuzzi, F. Bonifazi, I. Labastida, L. O. B. da Silva Santos,
M. Roos, The “a” of fair–as open as possible, as closed as necessary, Data Intelligence 2
(2020) 47–55.
[31] K. Joiner, R. Lusch, Evolving to a new service-dominant logic for health care (2016).
[32] T. L. Beauchamp, J. F. Childress, et al., Principles of biomedical ethics, Oxford University</p>
      <p>Press, USA, 2001.
[33] T. Ting, Privacy and confidentiality in healthcare delivery information system, in:
Proceedings 12th IEEE Symposium on Computer-Based Medical Systems (Cat. No. 99CB36365),
IEEE Computer Society, 1999, pp. 2–2.
[34] Y. Y. Al-Salqan, Security and confidentiality in healthcare informatics, in:
Proceedings Seventh IEEE International Workshop on Enabling Technologies: Infrastucture for
Collaborative Enterprises (WET ICE’98)(Cat. No. 98TB100253), IEEE, 1998, pp. 371–375.
[35] K. Chassie, A private matter [privacy in society], IEEE Potentials 20 (2001) 26.
[36] E. D. Berlan, T. Bravender, Confidentiality, consent, and caring for the adolescent patient,</p>
      <p>Current opinion in pediatrics 21 (2009) 450–456.
[37] P. Hruby, Model-driven design using business patterns, Springer Science &amp; Business Media,
2006.
[38] G. L. Geerts, W. E. McCarthy, Policy-level specifications in rea enterprise information
systems, Journal of Information Systems 20 (2006) 37–63.
[39] EUCTregister, Eu clinical trials register, 2022. URL: https://www.clinicaltrialsregister.eu/
ctr-search/trial/2017-002976-24/NL.
[40] ForeCare, Philips enhancing patient care and collaboration, 2018. URL:
https://www.usa.philips.com/healthcare/resources/landing/interoperability-solutions#
triggername=close_it.
[41] Nictiz, Electronic patient data exchange netherlands, 2022. URL: https://www.nictiz.nl/
english/exchange-of-electronic-patient-data-in-the-netherlands/.
[42] HL7, Health level seven, 2018. URL: https://www.hl7.nl/overhl7.html.
[43] NictizAim, Dutch organization for digital care info share, 2022. URL: https://www.nictiz.</p>
      <p>nl/over-nictiz/.
[44] CyberLab, Patient care with cyberlab, 2018. URL: https://www.clinisysgroup.com/nl/nl/
solution/cyberly-nl/.
[45] Diagnostiek4u, Laboratory and medical diagnostics, 2018. URL: https://diagnostiekvooru.</p>
      <p>nl/.
[46] ZorgNetOost value driven care, Philips enhancing patient care and collaboration, 2022.</p>
      <p>URL: https://zorgnetoost.nl/wat-we-doen/.
[47] ZONMWnl2, Zonmwnl: Strengthening impact in the netherlands,
2022. URL: https://gallery.mailchimp.com/7fa42547078f2cac7d96896f5/files/
54710d19-6a40-4f27-a8c9-c3a15a010a59/Wendy_paper.pdf.
[48] ZenodoEU, Zenodo a vision for open science, 2022. URL: https://zenodo.org/record/
1491303#.Yha14ojMJPY.
[49] Firely, Bring fhir to life with firely, 2017. URL: https://fire.ly/.
[50] CLSI, global standard in laboratory medicine, 2022. URL: https://clsi.org/.
[51] L. Jamian, L. Wheless, L. J. Croford, A. Barnado, Rule-based and machine learning
algorithms identify patients with systemic sclerosis accurately in the electronic health
record, Arthritis research &amp; therapy 21 (2019) 1–9.
[52] NEN7510, Nen 7510 certification information security, 2021. URL: https:
//www.dnv.nl/services/nen-7510-certificering-informatiebeveiliging-31846?msclkid=
0983a13078761ddfa84cc32f4dead50e&amp;utm_source=bing&amp;utm_medium=cpc&amp;utm_
campaign=11.%20S_NB_Informatiebeveiliging_NEN7510&amp;utm_term=NEN%207510&amp;
utm_content=NEN%207510.
[53] WMAdec, Declaration on health databases and biobanks
ethics, 2017. URL: https://www.wma.net/policies-post/
wma-declaration-of-taipei-on-ethical-considerations-regarding-health-databases-and-biobanks/.
[54] A. Anil Sinaci, F. Núñez-Benjumea, M. Gencturk, M.-L. Jauer, T. Deserno, C. Chronaki,
G. Cangioli, C. Cavero-Barca, J. M. Rodríguez-Pérez, M. M. Pérez-Pérez, et al., From raw
data to fair data: The fairification workflow for health research (2020).
[55] FHIR, Fast health interoperability resources, 2017. URL: http://www.fhir.org/.
[56] Medlon, A unilab company, 2017. URL: https://www.medlon.nl/.
[57] ISO15189, Medical lab requirements, 2017. URL: https://www.iso.org/standard/56115.html.
[58] ISO22870, Requirements for quality and competence, 2017. URL: https://www.iso.org/obp/
ui/#iso:std:iso:22870:ed-1:v1:en.
[59] NEN7522, Developing and managing standards, 2021. URL: https://www.nen.nl/
nen-7522-2020-ontw-nl-276028.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>EUDATASTRATEGY</surname>
          </string-name>
          ,
          <article-title>Shaping europe's digital future</article-title>
          ,
          <year>2022</year>
          . URL: https://digital-strategy. ec.europa.eu/en.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>GOFAIR</surname>
          </string-name>
          , Go fair initiative,
          <year>2022</year>
          . URL: https://www.go-fair.org/go-fair-initiative/ governance/steering-committee/.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>S.</given-names>
            <surname>Collins</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Genova</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Harrower</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Hodson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Jones</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Laaksonen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Mietchen</surname>
          </string-name>
          , R. Petrauskaitė,
          <string-name>
            <given-names>P.</given-names>
            <surname>Wittenburg</surname>
          </string-name>
          ,
          <article-title>Turning fair into reality: Final report and action plan from the european commission expert group on fair data</article-title>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M. D.</given-names>
            <surname>Wilkinson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumontier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I. J.</given-names>
            <surname>Aalbersberg</surname>
          </string-name>
          , G. Appleton,
          <string-name>
            <given-names>M.</given-names>
            <surname>Axton</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Baak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Blomberg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.-W.</given-names>
            <surname>Boiten</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. B. da Silva</given-names>
            <surname>Santos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. E.</given-names>
            <surname>Bourne</surname>
          </string-name>
          , et al.,
          <article-title>The fair guiding principles for scientific data management and stewardship</article-title>
          ,
          <source>Scientific data 3</source>
          (
          <year>2016</year>
          )
          <fpage>1</fpage>
          -
          <lpage>9</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>A.</given-names>
            <surname>Jacobsen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Kaliyaperumal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. O. B. da Silva</given-names>
            <surname>Santos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Mons</surname>
          </string-name>
          , E. Schultes,
          <string-name>
            <given-names>M.</given-names>
            <surname>Roos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Thompson</surname>
          </string-name>
          ,
          <article-title>A generic workflow for the data fairification process</article-title>
          ,
          <source>Data Intelligence</source>
          <volume>2</volume>
          (
          <year>2020</year>
          )
          <fpage>56</fpage>
          -
          <lpage>65</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <article-title>[6] FAIRroadmap, Roadmap for fair data sharing</article-title>
          ,
          <year>2022</year>
          . URL: https://www.glopid-r.org/ wp-content/uploads/2019/06/glopid-r
          <article-title>-roadmap-for-data-sharing</article-title>
          .pdf.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <issue>GDPRrecital53</issue>
          ,
          <article-title>General data protection regulation recital 53, 2021</article-title>
          . URL: https://gdpr.eu/ recital-53
          <string-name>
            <surname>-</surname>
          </string-name>
          processing
          <article-title>-of-sensitive-data-in-health-and-social-sector/.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <issue>GDPRrecital5</issue>
          ,
          <article-title>General data protection regulation recital 5, 2021</article-title>
          . URL: https://gdpr-info. eu/recitals/no-
          <issue>5</issue>
          /.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>GDPRobjective</surname>
          </string-name>
          ,
          <article-title>General data protection regulation objective</article-title>
          ,
          <year>2021</year>
          . URL: https://gdpr.eu/ article-1
          <article-title>-subject-matter-and-objectives-overview/.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>W. M. van der Aalst</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Bichler</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Heinzl</surname>
          </string-name>
          ,
          <source>Responsible data science</source>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>RDS</surname>
          </string-name>
          ,
          <source>Responsible data science</source>
          ,
          <year>2017</year>
          . URL: https://redasci.org/.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>J. R.</given-names>
            <surname>Helliwell</surname>
          </string-name>
          ,
          <article-title>Fact and fair with big data allows objectivity in science: The view of crystallography, Structural Dynamics 6 (</article-title>
          <year>2019</year>
          )
          <fpage>054306</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>S. A.</given-names>
            <surname>Sohail</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. A.</given-names>
            <surname>Bukhsh</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. van Keulen</surname>
          </string-name>
          ,
          <article-title>Multilevel privacy assurance evaluation of healthcare metadata</article-title>
          ,
          <source>Applied Sciences</source>
          <volume>11</volume>
          (
          <year>2021</year>
          )
          <fpage>10686</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>S. A.</given-names>
            <surname>Sohail</surname>
          </string-name>
          ,
          <article-title>Normative and empirical evaluation of privacy utility trade-of in healthcare</article-title>
          ,
          <source>in: Proceedings of the 33rd International Conference on Advanced Information Systems Engineering CAiSE</source>
          , volume
          <volume>21</volume>
          ,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>S. A.</given-names>
            <surname>Sohail</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. A.</given-names>
            <surname>Bukhsh</surname>
          </string-name>
          , M. van
          <string-name>
            <surname>Keulen</surname>
            ,
            <given-names>J. G.</given-names>
          </string-name>
          <string-name>
            <surname>Krabbe</surname>
          </string-name>
          ,
          <article-title>Identifying materialized privacy claims of clinical-care metadata share using process-mining and rea ontology</article-title>
          ,
          <source>in: Proceedings of the 15th Int'l Workshop on Value Modelling and Business Ontologies</source>
          ,
          <string-name>
            <surname>VMBO</surname>
          </string-name>
          ,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>S. A.</given-names>
            <surname>Sohail</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Krabbe</surname>
          </string-name>
          ,
          <string-name>
            <surname>P. de Alencar Silva</surname>
            ,
            <given-names>F. A.</given-names>
          </string-name>
          <string-name>
            <surname>Bukhsh</surname>
          </string-name>
          ,
          <article-title>Privacy value modeling: A gateway to ethical big data handling</article-title>
          ,
          <source>in: 14th International Workshop on Value Modelling and Business Ontologies</source>
          ,
          <string-name>
            <surname>VMBO</surname>
          </string-name>
          <year>2020</year>
          , CEUR,
          <year>2020</year>
          , pp.
          <fpage>5</fpage>
          -
          <lpage>15</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <surname>GDPR</surname>
          </string-name>
          ,
          <article-title>General data protection regulation</article-title>
          ,
          <year>2021</year>
          . URL: https://gdpr-info.eu/.
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <article-title>DPO, data-protection-</article-title>
          <string-name>
            <surname>oficer</surname>
          </string-name>
          ,
          <year>2018</year>
          . URL: https://www.itgovernance.
          <article-title>eu/nl-nl/ data-protection-oficer-dpo-under-the-gdpr-nl.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <surname>DUTCH-DPA</surname>
          </string-name>
          , autoriteitpersoonsgegevens,
          <year>2018</year>
          . URL: https://autoriteitpersoonsgegevens. nl/en/about-dutch
          <article-title>-dpa/board-dutch-dpa.</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>