<!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>X (T. Karunaratne);</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Holistic understanding of digital transformation of health care system as a point-of-departure for system requirements specification</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Thashmee Karunaratne</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Workneh Ayele</string-name>
          <email>workneh@dsv.su.se</email>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Aron Larsson</string-name>
          <email>aron@dsv.su.se</email>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Luigi Assom</string-name>
          <email>luigi.assom@dsv.su.se</email>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Gisele Züniga</string-name>
          <email>gisele.zuniga@actadig.se</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Actadig</institution>
          ,
          <addr-line>Stockholm</addr-line>
          ,
          <country country="SE">Sweden</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Dept. of Communication, Quality Management and Information Systems, Mid Sweden University</institution>
          ,
          <addr-line>851 70 Sundsvall</addr-line>
          ,
          <country country="SE">Sweden</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Dept. of Computer and Systems Sciences, Stockholm University</institution>
          ,
          <addr-line>164 40 Kista</addr-line>
          ,
          <country country="SE">Sweden</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Proceedings EGOV-CeDEM-ePart conference</institution>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>School of Industrial Engineering and Management, Royal Institute of Technology/KTH</institution>
          ,
          <addr-line>100 44 Stockholm</addr-line>
          ,
          <country country="SE">Sweden</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2023</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0001</lpage>
      <abstract>
        <p>The challenges regarding harmonised interoperable e-health services are enormous due to the complexity of the domain, comparatively high demands of privacy and security, implications of storing, sharing, and managing health data as well as unclear definitions and standards for patient's electronic health records. Therefore, the advantages of digitalisation are yet to reach the end user-patient, especially in the emergent regions where digital infrastructure is limited. The focus is on the north and northeast regions of Brazil, where a holistic understanding of the requirements for a digital transformation of the health care system is explored through the lens of an expert panel using a Delphi methodology, complemented by a comparison with related innovations in the digital health domain.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Digital transformation</kwd>
        <kwd>health care</kwd>
        <kwd>system requirements</kwd>
        <kwd>patient centricity 1</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        For the healthcare domain, the complexity of the digital transformation process is high due
to the high sensitivity of the health data and the privacy and security reservations
concerning the domain [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Digital transformation of health units, including the processes
for managing personal electronic medical records of the patient, can become an essential
enabler for the efficient and effective provision of public health service. However,
challenges are encountered in every step of the process of digital transformation due to the
complexity and fragmentation of the legal, technical, se-mantic, and business demand and
supply, which, oftentimes, are constrained by the policies and practices of the healthcare
domain [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ]. The gap is growing constantly as contemporary literature pinpoints. The
impact is even higher in emerging and rural regions, where the resources, funds and health
service infrastructure are limited. While the typical digital platform solutions available
today are also not created from a human-centred patient perspective [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], it is essential to
understand the prerequisites for eHealth, prior to instrumenting solutions, through the
lenses of answers to questions such as “what is required to make a patient’s journey more
effortless and efficient”, “how a patient take a more active role in managing their
healthcare”, “how can a patient mitigate treatment risks and lower his/her anxiety about
illnesses and diseases”, and “how can the access to healthcare and interaction with
healthcare professionals be improved”.
      </p>
      <p>
        The project Electronic Identity-Enabled Standardized and Harmonized Health Record
Management (eSHARE) therefore tries to understand the demands of the complex context
of digital transformation of the health system through a feasibility pre-study [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Firstly, it
aims to understand the context and local practices to elicit the requirements and obligations
for patient-centricity, i.e. letting the experiences and contextual know-how of patients serve
as the backbone for system design (cf. [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]), followed by an analysis of the impact that a
patient-centric approach preserving privacy and security of patient data has on digital
identification in the local healthcare delivery system and a harmonised standardised health
records management. This paper presents the steps taken towards forming a minimum set
of requirements for an electronic health record management system, based on the legal and
ethical contexts together with national, regional, sectorial, and municipal healthcare
regulations and policies. The selected emerging region in this work is the north and
northeast regions of Brazil, where the technology infrastructure, the basic needs of the patients
and the literacy levels of the citizens differ widely compared to the other regions of the
country [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Study context</title>
      <p>
        Brazil’s Unified Health System (Sistema Único de Saúde - SUS) is mandated to provide equal
health services to all citizens, although regional finances and availability of professionals
have created a huge gap in the quality-of-care provisioning across different states. The
digital health strategy of Brazil predominantly aims at levelling up and leveraging efficient
and effective care provision. However, the digital solutions provided by the federal
government in support of the implementation are being pertained in diverse ways, due to
the federal government structure. In addition to the national digital health strategy, which
is the governing framework of digital transformation in the sector, operational strategies
for implementation and uptake at the municipal level are needed. Such local strategies
promote operational efficiency and effectiveness of the health service, transparency,
inclusion, and patient mobility aiming for an increase in patient satisfaction, and patient
meetings, fostering preventive health initiatives while attracting qualified healthcare
professionals [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>
        Despite improvements in the healthcare infrastructure, a great gap in the dissemination
of care facilities between rural and urban areas still exists [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Among other disparities, the
distribution of care units, the number of healthcare professionals, the provision of medicine
and special treatments including special care, as well as the technology maturity and
literacy among users are a few to mention. There is also a heterogeneous application of
digital tools in the current SUS, including an electronic health record system introduced by
the federal government [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Therefore, it is essential to understand the current landscape
and the services prior to proposing digital solutions for municipal healthcare services [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Method</title>
      <p>As described in the preceding section, an exploratory case study strategy is pursued to
understand the prerequisites for requirements elicitation within the context. The case itself
premises the features of an emerging region, where its current landscape of health service,
legal and strategic demands play a pivotal role in discerning and outlining the essential
prerequisites crucial for executing a successful digital health transformation. It intends to
function as a guiding baseline, systematically identifying the specific needs, technological
aspects, infrastructural demands, and potential challenges unique to the region, thereby
paving the way for an effective implementation strategy tailored to its distinctive context.</p>
      <sec id="sec-3-1">
        <title>3.1. The context and unit of analysis</title>
        <p>
          General aspects characterising the territorial context of Brazilian healthcare were explored
before setting up the empirical approach within specific regions in the north and northeast
(states of Maranhão and Para). While responsibilities are governed centrally by the federal
government, some are by the region (State), and the main operational unit is by the
municipality [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. Therefore, the unit of analysis in this study is a municipality in the selected
region. Maranhão is divided into 217 municipalities and Para in 144 municipalities, but it is
larger and more populous. The eSHARE project works with a consortium of 26
municipalities (CIM) from both states, collaborating on addressing common issues affecting
their region.
        </p>
        <p>Basic Health Units (Unidades Básicas de Saúde – UBS) form the foundation of primary
care, which provides preventive care, vaccinations, basic treatments, and health promotion
services to their communities. Each municipality typically has several UBS scattered across
its territory. An example is Family Care, which assigns multidisciplinary teams, such as
community health agents (ACS) and other professionals, to specific neighbourhoods,
villages, or regions, to provide more comprehensive and continuous care. Municipalities
may also specialise in outpatient clinics or centres for specific services, such as mental
health support, physical therapy, and other treatments. The hospitals and emergency care
units are typically located in the largest municipalities in the region (Unidades de Pronto
Atendimento - UPA), which manage more complex cases and emergencies. Each
municipality has a Health Secretariat responsible for overseeing and coordinating health
policies, it manages budget allocation, resource distribution, and implementation of
initiatives within its jurisdiction. The operational framework of the health sector within the
municipalities is oriented, by design, towards ensuring universal access to healthcare
services. Therefore, the requirement elicitation processes in this study are part of a focus
on the electronic health record (EHR) for primary and secondary care.</p>
        <p>Four stakeholder groups were identified to systematically capture the current landscape
of healthcare provisions: patients (who require continuous visits for health service);
healthcare professionals, such as doctors, nurses, and support staff in healthcare units;
leadership in municipalities (head of healthcare) and heads of information technology from
the municipalities in the selected regions. Patients were not directly included in the
respondent group, due to heterogeneity of their knowledge level in the area, which might
have led to difficulties in comprehension and a lack of awareness of patient rights in the
context of digital transformation. However, representatives from one patient organisation
were included.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Application of method</title>
        <p>
          A multi-method approach to engage expert groups consisting of health care professionals
active in the context of the case was adopted, complemented by a comparative study against
previously identified requirements for the health care domain. Similarly, Ref. [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] used a
questionnaire as their primary method in addition to document analysis, system analysis,
interviews, and observation as qualitative multimethod approaches to study healthcare
record records management in a study conducted in South Africa. The approach involved
two stages. Stage one included discussion sessions conducted with health research experts,
healthcare professionals (HCP), and the eSHARE project partners, to understand the current
situation and problems affecting the provision of healthcare services. The results of these
discussions were captured using a MIRO board as shown subsequently. Stage two focused
on prioritised requirements, selected by comparing the results from the discussion session
against literature and previously identified requirements, especially the Australian
platform “My Health Record Australia” [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] which is promoted as a world benchmark for
good practice in EHR systems.
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Expert group discussions</title>
        <p>
          The methodological base for the expert group discussions followed a Delphi approach, [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ].
The panel took place several times with four respondents and one discussant. Iterative
meetings allowed respondents more opportunities to gather the perspectives of patients,
HCPs, and system/technology administrators about the situation of the current healthcare
system and pinpoint their needs and demands for implementing an EHR system.
Privacyrelated requirements were elicited based on the privacy taxonomy [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] and privacy by
design [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ], ethical concerns-driven requirements [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ], and security-related requirements
[
          <xref ref-type="bibr" rid="ref14">14</xref>
          ].
        </p>
      </sec>
      <sec id="sec-3-4">
        <title>3.4. Ethical aspects</title>
        <p>
          The healthcare domain resides in one of the most sensitive data in public service where
utmost care should be taken when collecting and managing information of patients. We
have not measured or taken any sensitive or personal data from any participants involved
in data collection. This article addresses ethical concerns outlined in [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ], from data
collection to publication. For instance, informed consent was obtained from participants
before data collection. We informed participants about anonymity and the study's purpose.
Consequently, all participant data collected for this research is fully anonymised.
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Results and discussion</title>
      <sec id="sec-4-1">
        <title>4.1. Discussion sessions</title>
        <p>
          Expert discussions provided a holistic perspective on the needs related to the EHR systems,
pointing out varying levels of requirements granularity. The discussion sessions were held
in an informal setting and three rounds until no new knowledge appeared. The
collaboration with expert panels was facilitated by the MIRO platform [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ], explicating the
distinct perspectives on the requirements of patients, doctors, and, to a lesser extent, IT
administrators (see Fig. 1, accessible through [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ]).
        </p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Comparing with literature</title>
        <p>
          Ermakova et al. [17] were used as a basis to enrich security requirements, and [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] and [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]
for privacy requirements. Hence, the principle of privacy by design has been integrated as
a foundational element of a patient-centric EHR system and a necessity to comply with
stringent data protection regulations affecting the digital healthcare landscape. Ethical
standards and compliance with existing personal data protection laws are expected as a
default practice by users. The “Privacy by Default” aspect is added since it adds an extra
layer of pressure for the solution designers with a legal binding to put data safety in the first
place while creating the system [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. It is also advised that the default settings for the use
of cookies should only encompass consent elements deemed essential, rendering any
opt
        </p>
        <sec id="sec-4-2-1">
          <title>Data</title>
        </sec>
        <sec id="sec-4-2-2">
          <title>Confidentiality</title>
        </sec>
        <sec id="sec-4-2-3">
          <title>Access Control •</title>
          <p>•
•</p>
        </sec>
        <sec id="sec-4-2-4">
          <title>Data</title>
        </sec>
        <sec id="sec-4-2-5">
          <title>Ownership &amp;</title>
        </sec>
        <sec id="sec-4-2-6">
          <title>Integrity (Ownership)</title>
        </sec>
        <sec id="sec-4-2-7">
          <title>Security &amp;</title>
        </sec>
        <sec id="sec-4-2-8">
          <title>Compliance (Actions on data)</title>
        </sec>
        <sec id="sec-4-2-9">
          <title>Data</title>
        </sec>
        <sec id="sec-4-2-10">
          <title>Availability &amp; Management (Storage)</title>
          <p>•
•
•
•
•
•
•
•
•
•
•
•
•
•
and Information
(Security)</p>
          <p>Confidentiality
Anonymity
Control of access rights
Revocation of access rights
Fine-grained access control
(i.e. use of data that is only
necessary and permitted)
Access to patient data in
emergencies
Unlinkability (i.e. medical
actions and identities are
hidden from unauthorized
users)
Ownership of medical data
Integrity of patients’
personal information
Detection and prevention
of security violations
Non-repudiation
Authenticity and
authentication
Auditability
Archiving should be
facilitated.</p>
          <p>Fault tolerance
Provide non-stale or
up-todate data
Storage should last for
many years
out consent options invalid. Additionally, the system
must guarantee that personal
information is accessible solely to authorised individuals. Requirements were matched and
proposed in Table 1. Note that only the EHR System requirements are presented here.
Requirements for EHR Journal compliant with security and privacy</p>
        </sec>
        <sec id="sec-4-2-11">
          <title>Macro Area Requirements over Data Requirements EHR (Journal)</title>
          <p>•
•
•
•
•
•
•
•
•
•
•
•
•</p>
          <p>Secure authentication via trusted
electronic ID (eID)
Enable patients to set access control
(revoke, grant, deny, etc.) of their
health records after reviewing and
accepting access policy rights
Enable doctors to write, edit, and
update the medical records of their
patients only if they are granted access
to
Enable patients to decide which
healthcare provider organization can
view or update their health record or
documents
Enable healthcare workers to
supersede restrictions to access to
documents in case of emergency (e.g.
accepting policy regarding the
protection of patient privacy)
Patients can mark some health record
as personal/sensitive (optional)
Default access to patients’ records is
only accessible for registered
healthcare provider organizations
Notify patients when their health
records or documents are viewed,
updated, created, removed or
reinstated
Notify patients when the emergency
access function is invoked by
healthcare providers
Notify patients when their primary
doctor/healthcare provider is changed
Log health record access for
transparency and accountability.
Enable patients’ to limit sharing time
of documents via short-time access
code (e.g. healthcare provider must be
supplied with the code to access to
documents for the ongoing
medication)
The system shall activate the eID
authentication when healthcare
provider demands access to restricted
documents.</p>
        </sec>
        <sec id="sec-4-2-12">
          <title>System Performance (System)</title>
          <p>•
•
•</p>
          <p>Scalability
Usability
Efficiency
• Allows access emergency functions
(e.g. policy should include conditions
for allowing access
documents/information)
• Should allow add-ons integration for
patients’ management (e.g. connecting
with other health apps and
importing/exporting data; manage
subscriptions for integrating care)
• Should facilitate communication
between - Patient to doctor (1-1);
Patients to health forums (1-many);
share news for patients (1-many);
direct messaging (e.g. legal
compliance)</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Concluding remarks and further work</title>
      <p>This paper instrumented an approach to understanding in a holistic perspective of a digital
transformation of primary and secondary health care systems from a patient-centric
perspective. A preliminary requirement list was aggregated through discussion sessions
with experts and triangulated by desk research with the intention to be further trimmed
down through the lenses of healthcare stakeholders, commenting on the challenges of
dayto-day operations. It is evident that from the two exercises reported on in this paper alone,
the resulting requirement set remains too broad to tackle the development of a minimum
viable solution. Hence, we proceeded to distil these requirements into targeted use cases
from primary and secondary care as a crucial step to identify core functionalities that
directly address the more critical needs in the health care system.</p>
      <p>The set of use cases can be used to elaborate the requirement set for each case and lay
the ground for a patient-centric minimum viable solution for an electronic journal system
in the context of northern Brazil. Further work includes stipulating a tangible minimum
requirement set, identified through a series of participatory workshops using concrete
patient use cases as a backdrop for revealing the necessary information flow between the
actors involved in regular health care visits.</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgements</title>
      <p>This research is partially funded by Sweden's innovation agency Vinnova under the
framework of an international innovation collaboration with actors in Brazil in
collaboration with EMBRAPII research institute 2021 through eSHARE project (Grant no.
2021-04593). The partners of the eSHARE project Consórcio Intermunicipal Multimodal
CIM Brazil, and ARCT-PA Brazil are acknowledged for their contributions in the field work.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Belliger</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Krieger</surname>
            ,
            <given-names>D. J.:</given-names>
          </string-name>
          <article-title>The digital transformation of healthcare</article-title>
          .
          <source>Knowledge Management in Digital Change: New Findings and Practical Cases</source>
          , Springer International Publishing, pp.
          <fpage>311</fpage>
          -
          <lpage>326</lpage>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Kraus</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schiavone</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pluzhnikova</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Invernizzi</surname>
            ,
            <given-names>A. C.</given-names>
          </string-name>
          :
          <article-title>Digital transformation in healthcare: Analyzing the current state-of-</article-title>
          <string-name>
            <surname>research</surname>
          </string-name>
          ,
          <source>J. Bus. Res</source>
          .
          <volume>123</volume>
          ,
          <fpage>557</fpage>
          -
          <lpage>567</lpage>
          (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Chu</surname>
            ,
            <given-names>L. F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shah</surname>
            ,
            <given-names>A. G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rouholiman</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Riggare</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Gamble</surname>
            ,
            <given-names>J. G.</given-names>
          </string-name>
          :
          <article-title>Patient-centric strategies in digital health</article-title>
          . Digital Health: Scaling Healthcare to the World. Springer International Publishing, pp.
          <fpage>43</fpage>
          -
          <lpage>54</lpage>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <article-title>[4] eShare website</article-title>
          . https://www.su.se/english/research/research-projects/
          <article-title>eid-enabled-standardized-andharmonized-health-records-</article-title>
          <string-name>
            <surname>management-</surname>
          </string-name>
          e-share,
          <source>last accessed</source>
          <year>2024</year>
          /06/14
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Barbalho</surname>
            ,
            <given-names>I. M. P.</given-names>
          </string-name>
          et al.,
          <article-title>Electronic health records in Brazil: Prospects and technological challenges</article-title>
          ,
          <source>Front. Public Health</source>
          <volume>10</volume>
          , p.
          <volume>963841</volume>
          (
          <year>2022</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <article-title>[6] Brazil health care system profile</article-title>
          , https://www.commonwealthfund.org/international-healthpolicy-center/countries/brazil, last accessed
          <year>2024</year>
          /06/14
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Oliveira</surname>
            ,
            <given-names>A. B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>da Silva</surname>
            ,
            <given-names>A. M. B.</given-names>
          </string-name>
          :
          <article-title>Healthcare infrastructure and flows in the dissemination and care of Covid-19 patients in São Luís, Maranhão</article-title>
          . Brazil, GEOUSP
          <volume>27</volume>
          , (
          <year>2023</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Territorial</surname>
            <given-names>Unit -</given-names>
          </string-name>
          <article-title>an overview | ScienceDirect Topics</article-title>
          . https://www.sciencedirect.com/topics/computer-science/territorial-unit,
          <source>last accessed</source>
          <year>2023</year>
          /11/23
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Marutha</surname>
            ,
            <given-names>N. S.:</given-names>
          </string-name>
          <article-title>Studying medical records management in the public healthcare sector of South Africa using multi-method</article-title>
          .
          <source>Handbook of Research on Connecting Research Methods for Information Science Research</source>
          , pp.
          <fpage>404</fpage>
          -
          <lpage>424</lpage>
          ,
          <string-name>
            <given-names>IGI</given-names>
            <surname>Global</surname>
          </string-name>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <article-title>My Health Record for healthcare providers</article-title>
          . https://www.digitalhealth.gov.au/healthcareproviders/initiatives-and-programs/myhealth-record,
          <source>last accessed</source>
          <year>2024</year>
          /01/04
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Solove</surname>
            ,
            <given-names>D. J.:</given-names>
          </string-name>
          <article-title>A taxonomy of privacy</article-title>
          ,
          <source>Univ. Pa. Law Rev</source>
          .
          <volume>154</volume>
          (
          <issue>3</issue>
          ),
          <fpage>477</fpage>
          -
          <lpage>564</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Cavoukian</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Privacy by design in law, policy and practice</article-title>
          . https://policycommons.net/artifacts/1222006/privacy-by
          <article-title>-design-in-law-policy-</article-title>
          <string-name>
            <surname>andpractice</surname>
          </string-name>
          /1775082/, last accessed
          <year>2024</year>
          /01/04
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Ryan</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stahl</surname>
            ,
            <given-names>B. C.</given-names>
          </string-name>
          :
          <article-title>Artificial intelligence ethics guidelines for developers and users: clarifying their content and normative implications</article-title>
          ,
          <source>J. Inf. Commun. Ethics Soc</source>
          .
          <volume>19</volume>
          (
          <issue>1</issue>
          ),
          <fpage>61</fpage>
          -
          <lpage>86</lpage>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Ermakova</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fabian</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kornacka</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Thiebes</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Sunyaev</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Security and privacy requirements for cloud computing in healthcare: Elicitation and prioritization from a patient perspective</article-title>
          ,
          <source>ACM Trans. Manag. Inf. Syst. TMIS</source>
          <volume>11</volume>
          (
          <issue>2</issue>
          ),
          <fpage>1</fpage>
          -
          <lpage>29</lpage>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>Miro</surname>
          </string-name>
          . https://miro.com/,
          <source>last accessed</source>
          <year>2024</year>
          /01/04
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <article-title>Electronic health records blue print in Miro</article-title>
          . https://miro.com/app/board/uXjVPdKcDUA=,
          <source>last accessed</source>
          <year>2024</year>
          /01/04
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>