Mert Gencturk1*†
Gokce B. Laleci Erturkmen1†
A. Emre Akpinar1,2
Omid Pournik3
Bilal Ahmad3
Theodoros N. Arvanitis3,4
Wolfgang Schmidt-Barzynski5Tim Robbins4
Ruben Alcantud Corcoles6,7Pedro Abizanda6,7,8- 1SRDC Software Research & Development and Consultancy Corporation, Ankara, Türkiye
- 2Department of Computer Engineering, Middle East Technical University, Ankara, Türkiye
- 3Department of Electronic, Electrical and Systems Engineering, School of Engineering, University of Birmingham, Birmingham, United Kingdom
- 4Digital & Data Driven Research Unit, University Hospitals Coventry & Warwickshire NHS Trust, Coventry, United Kingdom
- 5University Hospital OWL, Bielefeld, Germany
- 6Geriatrics Department, Complejo Hospitalario Universitario de Albacete, Albacete, Spain
- 7CIBER de Fragilidad y Envejecimiento Saludable (CIBERFES), Instituto de Salud Carlos III, Madrid, Spain
- 8Facultad de Medicina de Albacete, Universidad de Castilla-La Mancha, Albacete, Spain
Introduction: The CAREPATH Project aims to develop a patient-centered integrated care platform tailored to older adults with multimorbidity, including mild cognitive impairment (MCI) or mild dementia. Our goal is to empower multidisciplinary care teams to craft personalized holistic care plans while adhering to evidence-based guidelines. This necessitates the creation of clear specifications for clinical decision support (CDS) services, consolidating guidance from multiple evidence-based clinical guidelines. Thus, a co-creation approach involving both clinical and technical experts is essential.
Methods: This paper outlines a robust methodology for generating implementable specifications for CDS services to automate clinical guidelines. We have established a co-creation framework to facilitate collaborative exploration of clinical guidelines between clinical experts and software engineers. We have proposed an open, repeatable, and traceable method for translating evidence-based guideline narratives into implementable specifications of CDS services. Our approach, based on international standards such as CDS-Hooks and HL7 FHIR, enhances interoperability and potential adoption of CDS services across diverse healthcare systems.
Results: This methodology has been followed to create implementable specifications for 65 CDS services, automating CAREPATH consensus guideline consolidating guidance from 25 selected evidence-based guidelines. A total of 296 CDS rules have been formally defined, with input parameters defined as clinical concepts bound to FHIR resources and international code systems. Outputs include 346 well-defined CDS Cards, offering clear guidance for care plan activities and goal suggestions. These specifications have led to the implementation of 65 CDS services integrated into the CAREPATH Adaptive Integrated Care Platform.
Discussion: Our methodology offers a systematic, replicable process for generating CDS specifications, ensuring consistency and reliability across implementation. By fostering collaboration between clinical expertise and technical proficiency, we enhance the quality and relevance of generated specifications. Clear traceability enables stakeholders to track the development process and ensure adherence to guideline recommendations.
1 Introduction
In the ever-evolving landscape of healthcare, the rising prevalence of multimorbidity combined with the complexity of medical knowledge poses significant challenges to clinical decision-making (1). Clinical guidelines, grounded in evidence-based practice, serve as essential tools for healthcare professionals in delivering optimal patient care (2). Nevertheless, the manual execution of these guidelines frequently leads to variations in practice, inefficiencies, and suboptimal outcomes, seemingly making the achievement of integrated care an overwhelming challenge (3, 4).
Integrated care is an organization-focused intervention that encompasses case-management, continuity of care, disease management, service integration, and multidisciplinary teamwork (5). It is designed to address the health and social needs of individuals living with multimorbidity, with the goal of reducing adverse healthcare outcomes, including potentially preventable hospitalizations (6). Older adults with multimorbidity can receive assistance in their own homes through Information and Communication Technologies (ICT) solutions. These solutions support them in their activities of daily living, help manage medical conditions and medications, and involve them in the healthcare process. Additionally, ICT solutions also improve physical activity and nutrition, reduce frailty, and facilitate health monitoring (7). While certain challenges remain to be addressed with these solutions, including concerns regarding data privacy and security threats, they hold significant potential for facilitating the transition from conventional medical practices to remote medicine (8, 9).
Computer-interoperable clinical guidelines play a crucial role in advancing such ICT solutions and digitizing healthcare (10). They enable the implementation of personalized clinical decision support (CDS) systems, aiding healthcare professionals in adhering to complex clinical protocols and facilitating guideline integration into daily practice. CDS systems integrate patient-specific data with evidence-based guidelines, providing real-time, personalized recommendations to healthcare providers. This integration holds great promise in streamlining clinical workflows, reducing errors, and ultimately enhancing patient outcomes (11, 12). Although CDS systems have undergone swift advancement since their initial implementation in the 1980s, their full adaptation in routine clinical practice has not yet been fully achieved for many reasons, such as ethical and legal issues, the intellectual challenge of creating knowledge, and technical dimensions of delivering CDS (13–15). Software engineers face challenges in understanding clinical guidelines due to a lack of medical expertise, which hampers their ability to automate CDS services, while clinicians without technical proficiency struggle to validate CDS implementations to ensure they align with guideline recommendations. The situation becomes more difficult when patients have multimorbidity conditions, because clinical guidelines are typically designed for individual conditions, and while they may address decision-making regarding other morbidities, they lack a systematic approach to identifying relationships between guidelines for different conditions (16).
The CAREPATH Project1 aims to deliver a patient-centered integrated care platform to meet the needs of older patients with multimorbidity, including mild cognitive impairment (MCI) or mild dementia (MD) (17). Dementia and MCI are two of the most debilitating chronic conditions in older adults, affecting approximately 7.3 and 20% of this population (18), respectively, and leading to high-impact healthcare needs. Integrated solutions are necessary to manage this condition, especially when other chronic conditions coexist. Notably, pharmacological and non-pharmacological treatments for diseases such as heart failure or diabetes may differ in older patients with dementia compared to the general population. Developing a patient-centered integrated care platform is challenging, as the vast majority of clinical guidelines that would inform these tools typically focus on a single condition (19).
To address this challenge, Robbins et al. (20) presented clinical requirements addressing the needs of this patient group in the form of a reference, consensus clinical guideline to be used for the CAREPATH project. The development of the guideline was undertaken by a Clinical Reference Group (CRG) formed by CAREPATH project clinical partners based in Germany, Spain, Romania, and the UK. After a review of the literature to identify suitable clinical guidelines, 52 guidelines covering a range of chronic conditions, multimorbidity, and co-morbidity were assessed for quality using the AGREE II methodology (21). Based on this, 25 final guidelines were selected for examination, approval, or disapproval, grouping, and consolidation by the project CRG through a modified Delphi process (22). The final agreed guidance and actions were collated into the master narrative consensus guideline. The CAREPATH consensus clinical guideline provides advice, information, and actions in the following areas: overarching principles of management, MCI and dementia, physical exercise, nutrition and hydration, common use of drugs, coronary artery disease, heart failure, hypertension, diabetes, chronic kidney disease, chronic obstructive pulmonary disease (COPD), stroke, sarcopenia, frailty, and caregiver support.
CAREPATH aims to deliver integrated care solutions to multi-disciplinary care teams, including health and social care providers, patients and their informal caregivers, enabling them to follow consensus guidelines in a personalized manner to create holistic care plans for older adults. The Adaptive Integrated Care Platform (AICP) is a clinician-facing application that allows healthcare professionals to review and update patient data retrieved from underlying Electronic Health Record (EHR) systems. It also enables them to assess personalized suggestions for editing the patient’s care plan, such as setting clinical goals, adding or updating interventions (e.g., medications, lab orders, referrals, and patient interventions like self-monitoring activities, diet, and exercise). AICP is supported by two important components: the Technical and Semantic Interoperability Suite (TIS/SIS), which facilitates integration with EHR systems (23), and CDS services that process consensus-based guideline rules to deliver personalized care plan suggestions. Once the care plan is created, the Patient Empowerment Platform (PEP), which was developed with the involvement of patients, informal caregivers, and healthcare professionals, provides personalized assistance and guidance to patients (24). It sends reminders about care plan goals and activities, presents educational materials to reinforce treatment adherence, and collects feedback from patients via Patient Reported Outcome Measures (PROMs) to conduct geriatric assessments. Finally, the Home and Health Monitoring Platform (H/HMP) provides environment-aware services to continuously collect real-time data for early detection of onset and changes in functioning, autonomy, and underlying cognitive and physiological functions of patients.
This paper introduces a robust methodology for generating implementable specifications of CDS services, aimed at automating clinical guidelines. Through a collaborative co-creation landscape, we enable clinical experts and software engineers to jointly examine guidelines and develop human-readable CDS specifications. Our approach addresses the challenge of translating guideline suggestions into actionable guidance, bridging the gap between clinical expertise and technical implementation. Key strengths include a repeatable process, traceability, and emphasis on human-readable specifications, ensuring accessibility and alignment with evidence-based practices. By fostering interdisciplinary collaboration, our methodology empowers teams to create CDS services that effectively automate clinical guidelines while tailoring care plans to individual patient needs. Our approach is based on international standards, namely CDS-Hooks and HL7 FHIR, targeting to enhance the interoperability and potential adoption of CDS services across diverse healthcare systems.
2 Method
The methodology devised to implement clinical decision support services automating evidence-based clinical guidelines consists of four steps along with the two preliminary steps as depicted in Figure 1. The selection of best practice guidelines and the creation of consensus clinical guidelines are pre-requisites of this approach. They have already been presented in (20), hence their detailed description is out of the scope of this paper. The list of the selected best practice guidelines in CAREPATH is provided in (25–49). However, it should be noted that the methodology explained in this paper can be applied to any type and number of clinical guidelines, so the selection of guidelines is not crucial for the subsequent downstream process.
Figure 1. Overview of the methodology for transforming evidence-based clinical guidelines into implementable clinical decision support services.
In the following subsections, we explain the details of the definition of flowchart-based rules, the definition of CDS rules in human-readable format, the definition of clinical concepts, and the preparation of CDS Hooks card templates.
2.1 Definition of flowchart-based rules
In the first step, the consensus guideline has been converted into flowchart-based rules, allowing integration into the digital platform for delivering care to dementia patients with multimorbidity. We attempted to formulate the sentences in the consensus guideline as flowchart rules, endeavoring to identify all clinical concepts. Close cooperation between technical personnel and CRG members was carried out to clearly assess the technical feasibility and clinical effectiveness of conversion of the narrative guideline into a flowchart. We have discussed and agreed on which parts of the consensus guideline can aid the clinicians if automated as a clinical decision support service integrated into daily care practices. As a first step to create flowcharts with decision points to assess patient data, we have identified all the clinical concepts involved in textual guideline definitions. For each clinical concept, it was discussed with the CRG group whether it constitutes a diagnosis, an assessment to be conducted by the physician, a laboratory result, a medication, a clinical procedure, or a scored assessment to be performed. It was also determined whether the information would be retrieved from the EHRs of the patient, or whether it cannot be obtained from the EHR and needs assessment through physician facing CAREPATH tools, such as the AICP. Consequently, jointly agreed-upon parts of the consensus guideline have been converted into flowchart rules that pave the way for the implementation of clinical decision support services.
In our methodology, we utilized the Unified Modeling Language (UML) Activity Diagrams to draw the flowcharts. While activity diagrams are primarily used in the design phase of software engineering to describe system behavior as a workflow, researchers have also begun utilizing them for modeling clinical workflows (50–52). Activity diagrams enable us to graphically describe what clinical action needs to take place in which condition in an easy way. It also allows describing sequential and parallel processes. Activity diagrams consist of several concepts, such as activity, action, transition (control flow and object flow), decision node, swimlane and partition, each of which has a different graphical notation. In our approach, we only utilized the following concepts with the provided purpose of usage:
• Initial node: A circle representing the beginning of a workflow consisting of a set of actions or activities.
• Control flow: An arrow showing the sequence of workflow.
• Decision node: A diamond representing a test condition, such as “Has the patient met his/her blood pressure goal?.” The control flow can only continue with one of the decision paths.
• Action/activity: A (rounded) rectangle representing an action from the consensus clinical guideline such as “Consider starting monotherapy with ACE inhibitors or Angiotensin II Receptor Blockers (ARBs) or Calcium channel blockers or Thiazide diuretics by also checking possible contraindications.”
• Final node: An encircled circle representing the end of a workflow.
Figure 2 illustrates an example of a flowchart generated for the hypertension diagnosis procedure. If a patient has not been diagnosed hypertensive, they have not been sent home for diagnosis confirmation, and their systolic blood pressure (SBP) value is above 140 mmHg or diastolic blood pressure (DBP) value is above 90 mmHg, the guideline recommends short-term self-monitoring of blood pressure levels. It also recommends setting a follow-up appointment to confirm diagnosis after 2–4 weeks. If the SBP is between 130 and 139 mmHg or DBP is between 85 and 89 mmHg, it recommends categorizing patient’s blood pressure as high-normal. If they are below 130 mmHg or 85 mmHg, respectively, it recommends normal categorization. On the other hand, if the patient has already been sent home, then based on the SBP and DBP values, patient’s blood pressure can also be categorized as Grade 1, Grade 2, or Grade 3. In either case, the guideline recommends diagnosing the patient as hypertensive.
Figure 2. An example of a flowchart based on Hypertension guideline. The yellow circle represents the start node, while the green circles represent the end node. Diamonds are used to represent decision nodes, and rounded rectangles represent actions.
2.2 Definition of CDS rules in human readable format
In the second step, we developed directly implementable specifications for clinical decision support services to automate the consensus clinical guideline. For this purpose, we opted for the CDS Hooks formalism, which is a standard specification for clinical decision support services published by HL7.2 It provides an API specification enabling synchronous, workflow-triggered CDS calls that return information and suggestions. The CDS Hooks specification describes a “hook”-based pattern for invoking decision support from within a clinician’s workflow. User activity within the clinician’s workflow triggers CDS hooks in real-time. When a triggering activity occurs, the CDS Client notifies each registered CDS service for the activity. These services must then provide near-real-time feedback about the triggering event. Each service receives basic details about the clinical workflow context (via the context parameter of the hook) along with any service-specific input data required (via the pre-fetch-template parameter).
In the CAREPATH context, this mechanism is utilized as follows (see Figure 3). CDSs in CAREPATH are employed to suggest personalized goals and interventions that can be put in a care plan based on the recommendations of clinical guidelines. AICP is responsible for calling the CDS services with important patient context data, crucial for personalizing suggestions. After presenting the suggestions to clinicians via user interfaces, the care plan of the patient can be created in a guided manner.
Figure 3. Use of CDS Hooks based services in CAREPATH architecture.
In CAREPATH, an HL7 FHIR-based interoperability approach is followed. All components utilize HL7 FHIR as a standard-based approach to represent patient data: the patient’s EHRs retrieved from local systems by TIS/SIS are mapped to FHIR and stored in an open-source HL7 FHIR Repository, namely onFHIR.io (53), serving as a shared patient data repository. Data collected from the patient’s home via home/health monitoring devices, such as vital signs, are stored as FHIR resources by H/HMP, and patient-collected data such as symptoms are represented as FHIR resources via PEP. AICP retrieves the relevant CDS input parameters from the FHIR repository as important patient context data and passes them to CDS services. In the CDS Hooks API, the patient data collected as FHIR data is passed as input to CDS services with the ‘pre-fetch’ parameter. The CAREPATH core data model conforms to HL7 FHIR Release 4, but the implemented architecture is not bound to this specific version. It can be easily adapted to accommodate later versions or modifications.
The response of CDS services can consist of textual recommendations communicated as information cards (which can be read and assessed by the clinician to create a care plan manually, such as adding medications based on the detailed guides about possible adverse reactions) or as directly reusable care plan components communicated as suggestion cards in conformance with the CDS Hooks API. In suggestion cards, the recommended goals and activities are represented as FHIR resources (such as MedicationRequest, Goal, Appointment resources) which can be used to constitute the care plan of the patient.
Based on the CDS Hooks standard, each CDS service can return any number of cards in response to the hook. Clinicians, as users, see these cards via AICP interfaces - one or more of each type – embedded in the workflow, and can interact with them as follows:
• Information cards provide text for the user to read. In our methodology, guidance from clinical guidelines, which may not be feasible or practical to automate but still provide crucial information to assist clinicians in creating individualized care plans, is represented as information cards. For example, in the Hypertension guideline, the guideline recommends discussing whether the patient is taking their medication as prescribed before considering changes to drug therapy, following the National Institute for Health and Care Excellence (NICE)’s guideline on medicines adherence (54). This guidance is presented as an information card and can be viewed by clinicians in a graphical user interface (UI) for reading and acting upon it. Example representations of information cards in CAREPATH AICP are illustrated in the Results section.
• Suggestion cards provide a specific recommendation for which the CDS Client renders a button that the user can click to accept. Clicking automatically populates the suggested change into the clinician’s UI. In CAREPATH, CDS services can recommend adding certain care plan activities such as Referral Requests, Appointment Requests, and Lab Test Orders. These are represented as FHIR resources (as detailed in Section 2.4) and presented to the user with checkboxes via AICP. Clinicians can add them directly to the patient’s care plan by clicking on the checkboxes next to these suggestions.
The flowcharts have been reviewed together with CRG members to determine the parts of the consensus guideline that should be presented as information cards or suggestion cards, in order to create a practical tool that can be easily utilized by clinicians as a part of their daily clinical workflow.
We created a formal template to document CDS Hooks specifications for delivering the advice, information, and actions suggested for each area addressed by the consensus clinical guideline as depicted in Figure 4.
Figure 4. A partial view of a CDS Hooks specification table, illustrating several CDS rules from Hypertension guideline.
In this table, each flowchart rule identified in the first step is represented as a row. The columns of this template can be summarized as follows:
• Each rule is identified with a unique identifier. We begin with the section title of the consensus guideline and assign a unique number for each rule, such as ‘Hypertension 1,’ ‘Hypertension 2,’ ‘Diabetes 1,’ ‘COPD 1’ and so on.
• Each rule has a context attribute, which is mostly informative and describes the current state of the patient for which the rule will be applied.
• Each rule has a purpose. The purpose field is critical for CDS specifications. We have examined and categorized the purpose of the advice, information, and actions suggested by the consensus guideline into the following categories:
○ Information
○ Goal management
○ Diagnosis
○ Lifestyle advice (Nutritional intervention and Physical exercise)
○ Drug treatment
○ Adverse events and medication contraindications
○ Symptom assessment
○ Complication management
○ Planning next visit
These purpose categories are utilized to group the suggestions, and separate CDS service implementations are done based on these categories. This facilitates presenting guidance from consensus guideline in a modular way in the user interfaces provided to clinicians. Different panels of the AICP pages are configured to be linked with different CDS service instances based on the purpose category, allowing clinicians to easily review the guidance provided by the consensus guideline.
• Each CDS rule has a triggering condition. Most of the time, for CDS rules automating clinical guideline suggestions, the triggering component is AICP. AICP calls the CDS services with the required input. Whenever the input parameters are updated from the user interface of AICP, the CDS services are triggered again.
• Rule descriptions are mainly retrieved from the consensus guideline and formalized to be easily converted into computer-interpretable rules. Each patient parameter represented as a clinical concept is enclosed within brackets (e.g., [SBP] designated for systolic blood pressure).
• Parameters represented as clinical concepts used in Rule descriptions within brackets are listed input parameters in the “Input as prefetch” column. These parameters need to be pre-fetched by the CDS client as FHIR resources from the FHIR repository and passed to the CDS services as an input. For this purpose, these parameters are first mapped to FHIR Resources, such as Condition, Observation, and Medication, and then represented as clinical concepts as explained in Section 2.3.
• Finally, the output of CDS rules is briefly described as CDS Hooks cards. Here in this table, only the titles, card numbers, and summaries are presented. As part of the CDS Hooks specification of CDS Services, there is a separate sheet where all the identified cards are clearly described, as presented in Section 2.4.
2.3 Definition of clinical concepts
Clear consensus on clinical concepts is a crucial step in CDS implementation for processing patient data to provide personalized suggestions. It is a step forward to create a common dictionary between clinical experts in CRG and technical experts who will implement CDS services. It is also essential to establish semantic interoperability with existing EHR systems to collect patient parameters in a machine-processable manner.
In this step, the parameters identified in rule descriptions and the “Input as prefetch” column are represented as clinical concept definitions (see Figure 5 for examples). Firstly, as CDS Hooks specifications require CDS parameters as HL7 FHIR resources, we have categorized clinical concepts as Condition, Observation, and Medication resources.
Figure 5. An excerpt from Hypertension clinical concepts table showcasing examples across different types.
The second important step is to bind each clinical concept to a code from international code systems. Based on discussions with CRG members, conditions have been coded either with ICD-10 or SNOMED CT codes, with categorization as diagnoses or symptoms. Medications are uniformly coded with ATC codes, while lab tests represented as FHIR Observations are coded with LOINC codes. Additionally, the agreed-upon unit of the lab test result observation is specified in reference to UCUM.
Assessments to be carried out by clinicians via AICP interfaces are also represented as FHIR Observation resources. These are coded with LOINC or SNOMED CT whenever possible. In instances where a direct mapping to a code in international code systems such as LOINC and SNOMED CT is not feasible, local codes have been created to designate these observations. The data types of these assessments, represented as FHIR Observation resources, are usually specified either as boolean Yes/No values, or as a value-set. Value-sets define a set of codes drawn from one or more code systems as possible values of these assessment observations. For example, such a value-set for representing smoking status observation is presented in Figure 5, where a set of LOINC codes is selected to represent possible values of a smoking status observation.
Additionally, the possible sources of these parameters have been identified. Some can be directly extracted from the patient’s EHR, while others require assessments during the visit, recorded via AICP. Some parameters can be retrieved from PEP, and others from H/HMP. This approach ensures that rule implementers can have a clear understanding of the clinical concepts to be processed by the CDS service implementation as parameters.
2.4 Preparation of CDS hooks card templates
After CDS rules are defined in a human-readable format, where the relevant clinical concepts are identified, the fourth step involves further detailing the specifications of CDS outputs identified in rule definitions. For this purpose, we have prepared CDS Hooks card templates. In successful responses, CDS Services respond with a 200 HTTP response containing an object that includes an array of cards.
Each of the cards identified in the Rules template is specified with all the details required in the CDS Hooks standard specification, as explained below. An example illustration of these in a user interface, such as AICP, is displayed in Figure 6.
• Summary: A short (usually one sentence) explanation of the suggestion, displayed in user interfaces as the title of the card.
• Detail: A detailed description sourced from the consensus clinical guideline. This description is displayed when the user clicks the arrow on the right side of the card title. It can be represented as plain text or in GitHub Flavored Markdown language.3 This field is optional.
• Source: The primary source of guidance for the decision support represented by the card. In CAREPATH, we provide the exact section number and page number of the referenced clinical guideline (e.g., “Holistic patient centered CAREPATH best practice guideline, Chapter 12.2 [pp. 40]”).
• Suggestions: An array of suggestions that allows a service to recommend a set of changes in the context of the current activity (e.g., adjusting the dose of a currently prescribed medication for the medication-prescribe activity). Each suggestion can contain an array of Actions, each defining a suggested action. Within a suggestion, all actions are logically ANDed together, meaning that selecting a suggestion selects all the actions within it. If there are alternative suggestions, separate suggestions should be created as part of the suggestions array. Each suggestion must have a label summarizing the suggested actions.
○ Each Action needs to have a type, which can be “create,” “delete,” or “update.” In the CAREPATH context, “create” means that the suggested actions (such as referral, appointment, lab test request) will be added as care plan activities to the care plan; “delete” means removing an existing care plan activity from the care plan, and “update” means updating an existing care plan activity in the care plan.
○ A human-readable description of the suggested action may be presented to the end-user, along with a description of the FHIR Resource that is suggested to be created, updated, or deleted. Therefore, each Action needs to have short title summarizing the suggested action. The presentation of suggestions and their corresponding actions within AICP is depicted in Figure 6.
Figure 6. Presenting CDS Hooks cards in a user interface, such as AICP.
If an Information card is suggested by the consensus guideline, then only the first three attributes (i.e., summary, detail, and source) are necessary. In other words, Information cards do not contain any suggestions, as their purpose is only to provide some information. An example of an information card definition as a part CAREPATH CDS specifications is presented in Card 4 in Table 1.
Table 1. An example of an Information Card (Card 4) and a CDS card for arranging a follow-up visit to assess treatment effectiveness, containing Appointment and Lab Order actions (Card 21).
Suggestion cards, on the other hand, always contain at least one Suggestion, which includes at least one Action. In CAREPATH, we have defined 7 types of actions, which are lab order, referral, appointment, patient activity, education material, goal, or medication. Within each Action, the exact FHIR Resource suggested to be added to the patient’s care plan should be present. In CAREPATH, we use the following FHIR resources to represent consensus guideline suggestions as care plan components: ServiceRequest, Appointment, CommunicationRequest, Goal, and MedicationRequest. The details of different types of Actions alongside the FHIR resources used in them are explained below.
• Lab Order Suggestions: Consensus guidelines may suggest lab orders to be requested as part of the care plan. These are represented as the ServiceRequest resource in HL7 FHIR. An example of a lab order suggestion action within a suggestion card is presented in Action 2 of the card in Table 1. With the ‘category’ attribute of the ServiceRequest resource, we identify it as a lab request, referencing our local ‘care-plan-activity-category’ value set. The specific lab test requested is specified via the ‘code’ attribute of the ServiceRequest resource. In the example in Table 1, Action 2 of Card 21 suggests a lab test order for ‘Creatinine [Mass/volume] in Serum or Plasma’, indicated by the ‘2160–0’ code from LOINC. Lab order categories are always indicated via a code from LOINC in CAREPATH. If there is guidance in the consensus guideline about when this lab test needs to be conducted, this is represented via the ‘occuranceDateTime’ attribute.
• Referral Suggestions: Consensus guidelines may suggest referrals to specialists as part of the care plan when a second opinion is needed. These are represented as ServiceRequest in HL7 FHIR.4 The ‘category’ attribute of the ServiceRequest resource identifies it as a referral request, referencing our local ‘care-plan-activity-category’ value set. When guidance is available in the consensus guideline, the specialty of the practitioner to whom the referral is targeted is specified via the ‘performerType’ attribute of the ServiceRequest resource. For example, Action 3 in Table 2 indicates a referral to a cardiologist via the ‘175651000’ code from SNOMED CT. Here, we always provide a code from the ‘performer-role’ value set defined by HL7.5 If there is guidance in the consensus guideline about when this referral needs to be conducted, this is represented via the ‘occuranceDateTime’ attribute.
• Appointment Suggestions: Consensus guidelines may suggest appointments to be scheduled as part of the care plan. These appointments can be for regular care plan review visits, to check the effects of treatments, or to discuss the results of referrals. They are represented as Appointment resource in HL7 FHIR.6 An example appointment action within a suggestion card is presented in Action 2 of the card in Table 2. The critical attributes are the appointment description and the proposed date, which is represented via the ‘start’ attribute.
• Patient Activity Suggestions: Consensus guidelines may suggest certain type of activities to be carried out by the patients as part of their care plans, such as physical exercises and self-measurement of vital signs. These are represented as ServiceRequest resources in HL7 FHIR. An example patient activity suggestion action within a suggestion card is presented in Action 1 of the card in Table 2. With the ‘category’ attribute of the ServiceRequest resource, we identify that it is a patient order, referencing our local ‘care-plan-activity-category’ value set. The specific activity type to be carried out is specified via the ‘code’ attribute of the ServiceRequest resource. In the example in Table 2, Action 1 suggests the patient to measure their blood pressure, indicated by the ‘85354–9’ code from LOINC in the ‘code’ attribute. If there is guidance in the consensus guideline about when this activity needs to be conducted, this is represented via the ‘occuranceDateTime’ attribute. In this example, the patient is asked to measure their blood pressure twice a day.
• Education Material Suggestions: Consensus guidelines may suggest educational materials to be assigned to the patient as a part of the care plan. These are represented as CommunicationRequest resources in HL7 FHIR.7 The payload attribute is utilized to refer to an online educational material that can be offered to the patient via the ‘payload.contentAttachment.url’ attribute. An example is presented in Action 1 and 2 of the Lifestyle Interventions card shown in Table 3.
• Goal Suggestions: Consensus guidelines may suggest personalized goals to be assigned to the patient as part of the care plan. For example, in the diabetes section of the consensus guideline, personalized HbA1C, blood pressure, and lipid targets are suggested based on the patient’s various parameters, such as glucose level, age, comorbidities, and recent lab test results. These goals are represented as Goal resources in HL7 FHIR.8 The objective of the goal is indicated via the ‘description.code’ attribute, referencing international code systems. In the example presented in Table 4, the code ‘135840009’ from SNOMED CT is used to specify that this is a ‘Blood Pressure monitoring’ goal. The specifics of the goal target are specified via the ‘target’ attribute, where the ‘target.measure’ attribute indicates that this is a goal for systolic blood pressure, referencing LOINC code ‘8480–6’, with the target values indicated via the ‘target.detailRange’ attributes between 130 and 140 mmHg.
• Medication Suggestions: Consensus guidelines may suggest adding, updating the dose, or discontinuing a medication as part of the personalized care plan for the patient. For example, in the hypertension section of the consensus guideline, if the patient cannot achieve their blood pressure goals while already on dual medication, the consensus guideline suggests considering a triple combination of ACEi/ARB, CCB, and diuretic, while also checking for possible contraindications. These medication recommendations can be represented as MedicationRequest resources in HL7 FHIR.9 In the example presented in Table 5, the first suggestion card recommends adding a beta-blocking agent. Other possible options can be added as additional alternative suggestion cards. The code “C07” from ATC is used to specify that the recommended drug is a beta-blocking agent. Possible side effects are presented as information cards, as depicted in Table 5. Considering that there could be too many options for the clinician to decide on, especially when considering possible side effects, it is also possible to represent medication recommendations as Information cards only. This enables the clinician to manually edit the medication plan via AICP after reviewing all the guidance provided. In CAREPATH, we have chosen to follow this approach to make the CDS specifications more concise.
Table 2. An example of a CDS card for the management of resistant hypertension, containing Referral, Appointment and Patient Activity actions.
Table 3. An example of a CDS card for offering lifestyle interventions for hypertensive patients, containing Communication Request actions.
Table 4. An example of a Goal suggestion CDS card.
Table 5. An example of a Medication suggestion CDS Card (Card 31) and a possible side effect CDS card (Card 38).
3 Results
3.1 Output CDS rules and CDS hooks cards
Following the presented methodology, we analyzed the CAREPATH consensus clinical guideline, which provides advice, information, and actions in the following areas: overarching principles of management, mild cognitive impairment and dementia, physical exercise, nutrition and hydration, common use of drugs, coronary artery disease, heart failure, hypertension, diabetes, chronic kidney disease, COPD, stroke, sarcopenia, frailty, and caregiver support. We drew flowcharts, defined CDS rules and clinical concepts, and finally produced detailed implementable CDS-Hooks specifications for CDS services automating the following sections:
• Recommendations for the management of Mild dementia and mild cognitive impairment
• Recommendations for the management of Physical exercise
• Recommendations for the management of Nutrition and hydration
• Recommendations for the management of Commonly used drugs
• Recommendations for the management of Coronary artery disease
• Recommendations for the management of Heart failure
• Recommendations for the management of Hypertension
• Recommendations for the management of Diabetes
• Recommendations for the management of Chronic kidney disease
• Recommendations for the management of Chronic obstructive pulmonary disease
• Recommendations for the management of Stroke
• Recommendations for the management of Sarcopenia and frailty
• Recommendations for the management of Caregiver support
The full specifications are provided in the Supplementary material. In Tables 6, 7, we summarize the results of this process. The rules have been categorized under the following nine categories based on the purpose of recommendations:
1. Diagnosis: Guideline recommendations for diagnosing a patient’s condition based on their current health parameters and status. For instance, hypertension guidelines recommend diagnosing hypertension if the patient has already undergone home diagnosis confirmation and their blood pressure remains higher than 139/89 mmHg.
2. Lifestyle advice: Guideline recommendations related to nutritional intervention, physical exercise, and smoking cessation.
3. Goal management: Guideline recommendations for assigning patients targets to achieve, such as maintaining systolic blood pressure between 130 and 140 mmHg or providing weight loss advice to adults with elevated blood pressure or hypertension who are overweight or obese.
4. Drug treatment: Guideline recommendations for initiating new medication therapy for newly diagnosed patients or adjusting existing medication therapy if disease progression is not controlled.
5. Adverse events and medication contraindications: Guideline recommendations for informing clinicians about possible adverse events and contraindications before starting a new medication therapy. For instance, the CAREPATH consensus clinical guideline recommends closely monitoring the impact of BP-lowering drugs on the well-being of the patient due to increased risk of adverse events (e.g., injurious falls) in older adults. When combination therapy is used, it suggests starting at the lowest available doses.
6. Information and guidance about disease management: Includes guidance for clinicians on important aspects of disease treatment associated with cognitive impairment and dementia, reminders about assessments needed before treatment planning and presenting useful information for sharing/discussion with patients and their caregivers. For example, “Before initiating pharmacological treatment for diabetes, the person’s cardiovascular status and risk should be assessed to determine whether they have chronic heart failure” or “Keeping the environment at home safe to reduce the risk of falling and injury.”
7. Symptom recording: For reminding clinicians to assess patient’s specific symptoms at certain times or under certain conditions. For example, diabetes guidelines recommend assessing symptoms such as distress, disabilities, depression, anxiety, disordered eating, visual and hearing impairments, cognitive capacities, and other geriatric syndromes using a Comprehensive Geriatric Assessment at the initial visit, at periodic intervals, and when there is a change in disease, treatment, or life circumstance, including caregivers and family members in this assessment.
8. Complication management and referrals: Recommendations for referring patients to other departments or specialists in case of suspected complications, emergencies, or when consultancy/expertise from another specialty is required. For example, in hypertension treatment, referral to a cardiologist is recommended to rule out secondary causes if recommended treatment strategies fail to lower blood pressure values. Additionally, referral to a respiratory disease specialist is recommended for diagnosing obstructive sleep apnea if the patient exhibits symptoms such as snoring, apnea, nocturia, nocturnal dyspnea, nighttime cardiovascular events, or resistant hypertension, along with daytime sleepiness. Moreover, a referral to emergency services is advised if the patient’s clinic blood pressure exceeds 180/110 mmHg.
9. Planning next visit: For scheduling follow-up appointments to evaluate patient’s adherence to care plan activities and their response to treatment.
Table 6. The number of rules defined for different categories in each section.
Table 7. The number of CDS Hooks cards defined for each section and the number of actions per type in the cards.
Table 6 presents the number of rules defined for each section of the holistic guideline based on these categories. In total, 296 CDS rules have been defined. Among them, 117 (40%) are related to drug treatment, 46 (16%) to information and guidance about management, 40 (13%) to diagnosis, 29 (10%) to lifestyle advice, and 64 (21%) to other categories. No rules have been defined for drug treatment in the Sarcopenia & frailty, Nutrition & hydration, Physical exercise, and Caregiver support sections, because these guidelines do not directly address the treatment of specific diseases. Similarly, no rules related to diagnosis, complication management, and referral exist in the Commonly used drugs, Nutrition & hydration, Physical exercise, and Caregiver support sections. In goal management, guidelines for Hypertension, Diabetes, Stroke and Chronic kidney disease recommend setting targets for systolic blood pressure, diastolic blood pressure, weight, HbA1c, fasting glucose, LDL cholesterol, HDL cholesterol, Total cholesterol, and Hemoglobin. Since the CAREPATH study mainly focuses on multimorbidity management in the elderly with dementia, the largest number of rules for information and guidance about management has been defined in the Mild dementia & mild cognitive impairment section.
In each CDS rule, there exists one or more CDS Hooks card to achieve the specific objective of that rule. Table 7 shows the number of CDS Hooks cards defined for each section and the number of actions in those cards per action type. In the CAREPATH study, we defined 326 CDS Hooks cards to implement 296 CDS rules. Among them, the majority of the cards (191 out of 326, 59%) appeared in the Hypertension, Diabetes, COPD, and Chronic kidney disease sections, followed by 38 (12%) in MD & MCI and 31 (10%) in the Heart failure sections.
As explained in the Methodology section, a CDS Hooks card can be an information card, meaning that there is no action in it, or it can contain suggestions in which there exists at least one action. In Table 7, the number of information cards in each section is presented in the “Information & Medication contraindication” row. In hypertension, there exist 17 medication contraindication rules, which are modeled as information cards in CAREPATH. The rest of the rows in the table show the number of actions per type in the other CDS Hooks cards. Here, there is an additional type, autofill, which has not been explained in the methodology. In CAREPATH, autofill CDS Hooks cards are intended to present guideline recommendations suggesting diagnosis or assessment of a patient based on a recent measurement. For instance, hypertension guidelines recommend diagnosing Bradycardia if the patient’s heart rate is less than 60 bpm, diagnosing Hyperkaliemia if the patient’s potassium level is more than 5.5 mmol/L or considering severe left ventricular dysfunction if the patient’s left ventricular ejection fraction is less than 40%.
3.2 Implementation of CDS engine
In CAREPATH, based on the CDS Service specifications presented in Section 2, software engineers have implemented the CDS services via a CDS Engine implementation in the Scala programming language. For each category in each section presented in Table 6, a CDS-Hooks-complaint REST endpoint has been implemented. For some categories that contain a considerable number of rules, such as drug treatment or information and guidance about management, multiple endpoints have been created. Consequently, a total of 65 CDS-Hooks-compliant REST endpoints have been implemented.
In CAREPATH, the patient data retrieved from EHRs, created via AICP, and collected from patients via H/HMP and PEP, are all represented in HL7 FHIR and maintained in a FHIR repository. Within the implementation of CDS-Hooks endpoints in Scala, the prefetch parameters have been expressed as FHIR queries, to retrieve the indicated patient input from a FHIR server, acting as the patient data store.
The CDS Hooks cards, represented as separate tables in the CDS specifications, have been defined as parametrized JSON files, using a template language, namely Mustache. These are instantiated for each patient by filling in the placeholders with patient-specific parameters by our CDS Engine. The CDS Logic, defined as rules in the CDS specifications, is implemented as rules defined via FHIR Path expressions, mapping retrieved input parameters to pre-defined CDS Hooks Template cards. The defined CDS Hooks cards and service definitions are available as open-source on GitHub10.
In CAREPATH, we have preferred a Scala-based implementation. However, given the open specifications presented in Section 2, Supplementary material, and CDS-Hooks standard specifications, any other programming language could have been used to realize the implementation of these RESTful CDS services. Clear, open specifications mapping the clinical concepts to FHIR resources and international code systems, and rules defined based on these clinical concepts, enabled engineers who do not have clinical expertise to easily realize CDS implementations.
3.3 Usage of CDSs in a real-word environment
The Adaptive Integrated Care Platform (AICP) is one of the core components of the CAREPATH system, facilitating collaborative management of the care of multimorbid patients with mild dementia. It serves as the direct interface to care team members, allowing for the definition, updating, reconciling, and sharing of care plans, as well as the utilization of clinical decision support modules supporting these operations. It provides healthcare professionals with relevant information to guide decisions in an effective way, both during follow-up visits and in initial diagnosis processes. AICP has been implemented as a Web application providing an easy-to-navigate dashboard for care team members to view the basic medical history of the patient along with the care plan lifecycle history. The AICP care plan management graphical user interfaces have been designed to integrate the CDS services and to present the suggestions coming from CDS services in the best possible manner to facilitate care plan editing in the guidance of evidence-based clinical guidelines. The design was made with the involvement of healthcare professionals. First, the user requirements were collected through interviews conducted with them. Then, based on the user requirements, several mockups were drawn. These mockups were presented to healthcare professionals and their feedback was received. At the end of a few rounds, the final design emerged.
The input parameters of CDS services may be retrieved from the EHRs of the patient, including the patient’s existing diagnosis, medications, and lab test results, from PEP for symptoms recorded, and from H/HMP for measurements retrieved from health devices. During the analysis of CDS services, we realized that some input parameters are clinical assessments which need to be carried out by the clinician during the visit with the patient. An example could be assessing “whether the patient’s condition is stable or not.”
AICP has been designed to provide a specific page for the management of each section, described in Section 3.1; e.g., Hypertension diagnosis/treatment, Diabetes diagnosis/treatment, CAD management etc., along with additional pages to support some common functionalities such as reviewing the current status of the patient (such as physical examination, review of lab results), providing overarching lifestyle and physical exercise recommendations, and reviewing the questionnaires assigned to the patient.
The care plan management pages have been divided into two main parts, as illustrated in Figures 7, 8. In Part A, the clinician is reminded about the important parameters that will affect personalized decisions about care plan goals and activity suggestions. These parameters have been identified in the third step of our methodology, which is the definition of clinical concepts. The values of these concepts are mostly retrieved from EHRs, and clinicians can amend them if necessary (e.g., manually adding new lab results). Clinicians can make new assessments, mostly for assessments that need to be carried out during that encounter. Figure 7 shows the first part of the Hypertension treatment page consisting of six different panels. In the first panel, the clinician examines the patient’s latest systolic and diastolic blood pressure measurements as well as the number of falls since the last visit. The clinician can also record new values for those fields. Based on the latest systolic and diastolic blood pressure values, the guideline recommends categorizing the patient as Grade 1. In the second panel, the lab results of the patient are presented. It should be noted that these panels do not present the full medical summary of the patient. For each section, such as hypertension management, only the lab results, conditions, symptoms, assessments, etc. that are necessary for clinical assessment in the context of this section (that are listed in the clinical concepts table of the respective CDS services) are presented. In the third panel, comorbidities are shown. In the example, the CDS services automating hypertension guideline recommended CKD diagnosis, because the patient’s eGFR value is less than 60 mL/min. In the fourth and fifth panels, assessments and symptoms are presented, respectively.
Figure 7. An example representation of clinical concepts identified during the definition of CDS rules in AICP pages.
Figure 8. An example representation of CDS Hooks Cards in AICP interfaces.
Based on the reviewed patient data and the provided clinical assessments in Part A, CDS services run in the background and provide personalized suggestions about what needs to be put in the care plan of the patient in Part B, such as goals (e.g., personalized systolic blood pressure, LDL cholesterol, HbA1c target), control appointments, lab test requests, referrals, medication requests, education materials, and patient orders (e.g., measuring blood pressure at home).
Figure 8 displays the implementation of Part B in the Hypertension treatment page, consisting of three panels. As explained in Section 2.4, in CAREPATH, we have chosen to represent medication recommendations as Information cards and enable the clinician to manually edit the medication plan. Therefore, in the Medication treatment panel, the medication-related guideline recommendations are presented under the medication list, and the clinician is provided with add, edit, and delete buttons to update the patient’s medication treatment plan.
In the Goal Overview panel, the clinician can see the most recent systolic and diastolic blood pressure measurements of the patient in a chart view, observe the patient’s adherence to the previous goals, and update the goals based on the guideline recommendations.
The guideline recommendations, selected by the CDS Engine based on the patient parameters provided in Part A, are presented at the end of the page. Clinicians can decide whether to add a suggested item to the care plan or not by clicking on the checkbox near it. If needed, they can edit their details (e.g., the date of a control appointment). In the example shown in Figure 8, the guideline recommended targeting systolic BP between 120 and 140 mmHg and diastolic BP below 80 mmHg for the patient who is under treatment. It also recommended arranging a follow-up visit in 1 month and ordering lab tests for eGFR and serum creatinine. Since the patient has resistant hypertension (because the patient did not meet his BP targets on triple therapy), the guideline also recommended short-term self-monitoring of blood pressure levels to confirm inadequate control of BP, setting a follow-up appointment to confirm resistant hypertension after 2–4 weeks, and a referral to cardiologist for ruling out secondary causes.
4 Discussion
This paper presents a methodology for generating implementable specifications for clinical decision support (CDS) services aimed at automating clinical guidelines. We have established a co-creation framework facilitating collaborative exploration of clinical guidelines by both clinical experts and software engineers. Through a systematic, traceable approach, our methodology enables the generation of open, human-readable CDS specifications. This open and traceable co-creation approach has especially helped us to address the challenges of automating multimorbidity guidelines. We have demonstrated that it is technically possible to consolidate suggestions from multiple conflicting guidelines and transform them into implementable specifications. We believe this methodology contributes to making healthcare more manageable for healthcare providers dealing with multiple chronic conditions and provides a practical example for future studies.
Understanding clinical guidelines poses a significant challenge for software engineers lacking medical expertise, hindering their ability to develop CDS services for automation (55). Conversely, clinicians without technical proficiency encounter difficulties in validating CDS implementations to ensure alignment with guideline recommendations. Our approach addresses these challenges by fostering interdisciplinary collaboration, allowing both groups to collectively translate clinical guideline suggestions into actionable directives for personalized care plan development.
Key strengths of our methodology include:
• Repeatable Process: Our methodology offers a systematic, replicable process for generating CDS specifications, ensuring consistency and reliability across implementations.
• Co-Creation Landscape: By establishing a collaborative environment, we facilitate synergy between clinical expertise and technical proficiency, enhancing the quality and relevance of generated specifications.
• Traceability: Our approach provides clear traceability, enabling stakeholders to track the development process and ensure adherence to guideline recommendations.
• Human-Readable Specifications: We emphasize the creation of human-readable specifications, enhancing accessibility and facilitating comprehension for stakeholders across disciplines.
• Actionable Guidance: Our methodology translates clinical guideline suggestions into actionable guidance, enabling the creation of personalized care plans tailored to individual patient needs.
By bridging the gap between clinical expertise and technical implementation, our methodology empowers interdisciplinary teams to develop CDS services that effectively automate clinical guidelines while ensuring alignment with evidence-based practices.
We have adopted a standardized approach guided by CDS Hooks Specifications, leveraging HL7 FHIR to define clinical concepts. Our methodology ensures clarity by precisely delineating the input/output parameters of CDS services in alignment with HL7 FHIR Resources, grounding clinical semantics within international code systems. This establishes a universal, shared lexicon—facilitating seamless communication between clinical and technical experts. Moreover, our clear specifications streamline the implementation of CDS services, as input parameters can be readily accessed from a FHIR repository via FHIR queries. By adhering to standards and facilitating easy mapping to FHIR-based implementations, our research enhances the interoperability and potential adoption of CDS services across diverse healthcare systems. This robust framework not only accelerates integration with external health IT systems but also paves the way for widespread implementation, thereby maximizing the impact of our research in clinical practice. In doing so, it complements prior studies facing challenges in disseminating and sharing knowledge artifacts for clinical decision support across different electronic health record platforms (56, 57).
CDS services for multimorbid older adults with MCI/MD need to address “whole-of-person” interventions to improve their quality of life (19), considering not only social issues but also physical and psychological difficulties (58). The CDS services implemented, following the methodology outlined in this paper, take a holistic approach to these patients, including specific healthcare conditions not typically found in guidelines, such as nutrition, exercise, frailty, and sarcopenia. Furthermore, they enable the entire healthcare team to participate in the care process using the same platform, considering not only patients’ diseases but also environmental factors, caregiver support, quality of life, and psychosocial conditions.
The importance of patient privacy and data security in healthcare delivery necessitates careful planning and robust protection measures, particularly in highly automated workflows (59). Although the methodology outlined in this paper allows for the automation of clinical guidelines by producing implementable specifications for CDS services, it is limited to semi-automation, hence it does not provide a methodology for full automation. Healthcare professionals are still required to review CDS recommendations, make decisions, and exercise judgment at critical decision points in the workflow.
In future work, the usability, safety and technology acceptance of the CAREPATH ICT platform, including the developed tools and implemented CDS services, will be evaluated in a Technical Validation and Usability (TVU) study. This study will involve 16 patients with their informal caregivers and 16 healthcare professionals. Additionally, a Clinical Investigation (CI) involving over 200 patients will be conducted. These evaluations will take place in four European countries (Spain, Romania, Germany and the United Kingdom) over a period of 2 years.
Data availability statement
The original contributions presented in the study are included in the article/Supplementary material, further inquiries can be directed to the corresponding author.
Author contributions
MG: Conceptualization, Methodology, Software, Writing – original draft. GL: Conceptualization, Methodology, Project administration, Software, Writing – original draft. AA: Software, Writing – original draft. OP: Software, Writing – review & editing. BA: Validation, Writing – review & editing. TA: Validation, Writing – review & editing. WS-B: Formal analysis, Investigation, Resources, Writing – review & editing. TR: Formal analysis, Investigation, Resources, Writing – review & editing. RA: Formal analysis, Investigation, Resources, Writing – review & editing. PA: Formal analysis, Investigation, Resources, Writing – review & editing.
Funding
The author(s) declare that financial support was received for the research, authorship, and/or publication of this article. This work presented in this paper was funded by the European Union’s Horizon 2020 research and innovation program under grant agreement No 945169.
Acknowledgments
The authors would like to acknowledge the support of the CAREPATH consortium.
Conflict of interest
MG, GL, and AA are employed by Software Research & Development and Consultancy Corporation.
The remaining authors declare that the research was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.
The author(s) declared that they were an editorial board member of Frontiers, at the time of submission. This had no impact on the peer review process and the final decision.
Publisher’s note
All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.
Supplementary material
The Supplementary material for this article can be found online at: https://www.frontiersin.org/articles/10.3389/fmed.2024.1386689/full#supplementary-material
• CAD_CDSHooksSpecifications.xlsx
• CareGiverSupport_CDSHooksSpecifications.xlsx
• CKD_CDSHooksSpecifications.xlsx
• CommonlyUsedDrugs_CDSHooksSpecifications.xlsx
• COPD_CDSHooksSpecifications.xlsx
• Diabetes_CDSHooksSpecifications.xlsx
• HF_CDSHooksSpecifications.xlsx
• Hypertension_CDSHooksSpecifications.xlsx
• MCI_CDSHooksSpecifications.xlsx
• NH_CDSHooksSpecifications.xlsx
• PhysicalExercise_CDSHooksSpecifications.xlsx
• SarcopeniaFrailty_CDSHooksSpecifications.xlsx
• Stroke_CDSHooksSpecifications.xlsx
Additionally, the custom Value Set for listing care plan activity categories is provided in the following document.
• ValueSet_CarePlanActivityCategories.xlsx
Footnotes
1. ^CAREPATH Project Website, https://www.carepath.care/.
2. ^CDS Hooks Specifications, https://cds-hooks.hl7.org/.
3. ^GitHub Flavored Markdown Spec, https://github.github.com/gfm/.
4. ^HL7 FHIR, Release 4, ServiceRequest Resource, http://hl7.org/fhir/r4/servicerequest.html.
5. ^HL7 FHIR, Release 4, Performer Role Value Set, https://build.fhir.org/valueset-performer-role.html.
6. ^HL7 FHIR, Release 4, Appointment Resource, http://hl7.org/fhir/r4/appointment.html.
7. ^HL7 FHIR, Release 4, Communication Request Resource, http://hl7.org/fhir/r4/communicationrequest.html.
8. ^HL7 FHIR, Release 4, Goal Resource, http://hl7.org/fhir/r4/goal.html.
9. ^HL7 FHIR, Release 4, Medication Request Resource, https://hl7.org/fhir/R4/medicationrequest.html.
10. ^CAREPATH CDS Specifications, https://github.com/srdc/carepath-cds-specifications.
References
1. Mercer, SW, Smith, SM, Wyke, S, O’Dowd, T, and Watt, GC. Multimorbidity in primary care: developing the research agenda. Fam Pract. (2009) 26:79–80. doi: 10.1093/fampra/cmp020
2. Lugtenberg, M, Burgers, JS, and Westert, GP. Effects of evidence-based clinical practice guidelines on quality of care: a systematic review. BMJ Qual Saf. (2009) 18:385–92. doi: 10.1136/qshc.2008.028043
3. Fischer, F, Lange, K, Klose, K, Greiner, W, and Kraemer, A. Barriers and strategies in guideline implementation—a scoping review In: S. Parthasarathy editor. Healthcare, vol. 4: MDPI (2016). 36.
4. Lichtner, G, Spies, C, Jurth, C, Bienert, T, Mueller, A, Kumpf, O, et al. Automated monitoring of adherence to evidenced-based clinical guideline recommendations: design and implementation study. J Med Internet Res. (2023) 25:e41177. doi: 10.2196/41177
5. Goodwin, N, Stein, V, and Amelung, V. What is integrated care? Handb Integr Care. (2021) 3-25. doi: 10.1007/978-3-030-69262-9
6. Peart, A, Barton, C, Lewis, V, and Russell, G. A state-of-the-art review of the experience of care coordination interventions for people living with multimorbidity. J Clin Nurs. (2020) 29:1445–56. doi: 10.1111/jocn.15206
7. Fares, N, Sherratt, RS, and Elhajj, IH. Directing and orienting ICT healthcare solutions to address the needs of the aging population In: A. Vitali editor. Healthcare, vol. 9: MDPI (2021). 147.
8. Chen, C, Ding, S, and Wang, J. Digital health for aging populations. Nat Med. (2023) 29:1623–30. doi: 10.1038/s41591-023-02391-8
9. Gilbert, S, Ricciardi, F, Mehrali, T, and Patsakis, C. Can we learn from an imagined ransomware attack on a hospital at home platform? NPJ Digital Med. (2024) 7:65. doi: 10.1038/s41746-024-01044-5
10. Riaño, D, Peleg, M, and Ten Teije, A. Ten years of knowledge representation for health care (2009–2018): topics, trends, and challenges. Artif Intell Med. (2019) 100:101713. doi: 10.1016/j.artmed.2019.101713
11. Kruse, CS, and Ehrbar, N. Effects of computerized decision support systems on practitioner performance and patient outcomes: systematic review. JMIR Med Inform. (2020) 8:e17283. doi: 10.2196/17283
12. Garg, AX, Adhikari, NK, McDonald, H, Rosas-Arellano, MP, Devereaux, PJ, Beyene, J, et al. Effects of computerized clinical decision support systems on practitioner performance and patient outcomes: a systematic review. JAMA. (2005) 293:1223–38. doi: 10.1001/jama.293.10.1223
13. Sutton, RT, Pincock, D, Baumgart, DC, Sadowski, DC, Fedorak, RN, and Kroeker, KI. An overview of clinical decision support systems: benefits, risks, and strategies for success. NPJ Digital Med. (2020) 3:17. doi: 10.1038/s41746-020-0221-y
14. Sittig, DF, Wright, A, Osheroff, JA, Middleton, B, Teich, JM, Ash, JS, et al. Grand challenges in clinical decision support. J Biomed Inform. (2008) 41:387–92. doi: 10.1016/j.jbi.2007.09.003
15. Mayo, AT, Myers, CG, Bucuvalas, JC, Feng, S, and Juliano, CE. Supporting robust teamwork-bridging technology and organizational science. N Engl J Med. (2023) 388:2019–21. doi: 10.1056/NEJMp2300172
16. Pournik, O., Ahmad, B., Despotou, G., Lim Choi Keung, S. N., Mohamad, Y., Gappa, H., et al. (2022). CAREPATH methodology for development of computer interpretable, integrated clinical guidelines. Proceedings of the 10th International Conference on Software Development and Technologies for Enhancing Accessibility and Fighting Info-exclusion, Lisbon, Portugal. (pp. 7–11).
17. Pournik, O, Ahmad, B, Lim Choi Keung, SN, Khan, O, Despotou, G, Consoli, A, et al. CAREPATH: developing digital integrated care solutions for multimorbid patients with dementia. Stud Health Technol Inform. (2022) 295:487–90. doi: 10.3233/SHTI220771
18. Bacigalupo, I, Mayer, F, Lacorte, E, Di Pucchio, A, Marzolini, F, Canevelli, M, et al. A systematic review and meta-analysis on the prevalence of dementia in Europe: estimates from the highest-quality studies adopting the DSM IV diagnostic criteria. J Alzheimers Dis. (2018) 66:1471–81. doi: 10.3233/JAD-180416
19. Lugtenberg, M, Burgers, JS, Clancy, C, Westert, GP, and Schneider, EC. Current guidelines have limited applicability to patients with comorbid conditions: a systematic analysis of evidence-based guidelines. PLoS One. (2011) 6:e25987. doi: 10.1371/journal.pone.0025987
20. Robbins, T. D., Muthalagappan, D., O’Connell, B., Bhullar, J., Hunt, L. J., Kyrou, I., et al. (2022). Protocol for creating a single, holistic and digitally implementable consensus clinical guideline for multiple multi-morbid conditions. Proceedings of the 10th International Conference on Software Development and Technologies for Enhancing Accessibility and Fighting Info-exclusion, Lisbon, Portugal. (pp. 1–6).
21. Dans, AL, and Dans, LF. Appraising a tool for guideline appraisal (the AGREE II instrument). J Clin Epidemiol. (2010) 63:1281–2. doi: 10.1016/j.jclinepi.2010.06.005
22. Custer, RL, Scarcella, JA, and Stewart, BR. The modified Delphi technique-a rotational modification. Vocat Tech Educ. (1999) 15:04521022. doi: 10.21061/jcte.v15i2.702
23. Pournik, O, Ahmad, B, Lim Choi Keung, SN, Peake, A, Rafid, S, Tong, C, et al. Interoperable E-health system using structural and semantic interoperability approaches in CAREPATH In: O Mantas, P Gallos, E Zoulias, A Hasman, MS Househ, and M Charalampidou, et al., editors. Healthcare transformation with informatics and artificial intelligence : IOS Press (2023). 608–11.
24. Gencturk, M., Laleci Erturkmen, G. B., Gappa, H., Schmidt-Barzynski, W., Steinhoff, A., Abizanda, P., et al. (2022). The design of a mobile platform providing personalized assistance to older multimorbid patients with mild dementia or mild cognitive impairment (MCI). Proceedings of the 10th International Conference on Software Development and Technologies for Enhancing Accessibility and Fighting Info-exclusion, Lisbon, Portugal. (pp. 37–43).
25. Muth, C, Blom, JW, Smith, SM, Johnell, K, Gonzalez-Gonzalez, AI, Nguyen, TS, et al. Evidence supporting the best clinical management of patients with multimorbidity and polypharmacy: a systematic guideline review and expert consensus. J Intern Med. (2019) 285:272–88. doi: 10.1111/joim.12842
26. National Institute for Health and Care Excellence. Multimorbidity: clinical assessment and management. NICE guideline [NG56] (2016). Available at: https://www.nice.org.uk/guidance/ng56 (Accessed 2024-04-22)
27. Petersen, RC, Lopez, O, Armstrong, MJ, Getchius, TS, Ganguli, M, Gloss, D, et al. Practice guideline update summary: mild cognitive impairment: report of the guideline development, dissemination, and implementation Subcommittee of the American Academy of neurology. Neurology. (2018) 90:126–35. doi: 10.1212/WNL.0000000000004826
28. Atherton, JJ, Sindone, A, De Pasquale, CG, Driscoll, A, MacDonald, PS, Hopper, I, et al. National Heart Foundation of Australia and Cardiac Society of Australia and New Zealand: guidelines for the prevention, detection, and management of heart failure in Australia 2018. Heart Lung Circ. (2018) 27:1123–208. doi: 10.1016/j.hlc.2018.06.1042
29. McDonagh, TA, Metra, M, Adamo, M, Gardner, RS, Baumbach, A, Böhm, M, et al. 2021 ESC guidelines for the diagnosis and treatment of acute and chronic heart failure: developed by the task force for the diagnosis and treatment of acute and chronic heart failure of the European Society of Cardiology (ESC) with the special contribution of the heart failure association (HFA) of the ESC. Eur Heart J. (2021) 42:3599–726. doi: 10.1093/eurheartj/ehab368
30. Umemura, S, Arima, H, Arima, S, Asayama, K, Dohi, Y, Hirooka, Y, et al. The Japanese Society of Hypertension guidelines for the management of hypertension (JSH 2019). Hypertens Res. (2019) 42:1235–481. doi: 10.1038/s41440-019-0284-9
31. National Institute for Health and Care Excellence. Chronic obstructive pulmonary disease in over 16s: diagnosis and management. NICE guideline [NG115] (2019). Available at: https://www.nice.org.uk/guidance/ng115 (Accessed 2024-04-22)
32. Ismail, Z, Black, SE, Camicioli, R, Chertkow, H, Herrmann, N, Laforce, R Jr, et al. Recommendations of the 5th Canadian consensus conference on the diagnosis and treatment of dementia. Alzheimers Dement. (2020) 16:1182–95. doi: 10.1002/alz.12105
33. Frederiksen, KS, Cooper, C, Frisoni, GB, Frölich, L, Georges, J, Kramberger, MG, et al. A European academy of neurology guideline on medical management issues in dementia. Eur J Neurol. (2020) 27:1805–20. doi: 10.1111/ene.14412
34. National Institute for Health and Care Excellence. Dementia: assessment, management and support for people living with dementia and their carers. NICE guideline [NG97] (2018). Available at: https://www.nice.org.uk/guidance/ng97 (Accessed 2024-04-22)
35. World Health Organization. mhGAP Intervention Guide – Version 2.0: for mental, neurological and substance use disorders in non-specialized health settings (2019). Available at: https://www.who.int/publications/i/item/9789241549790 (Accessed 2024-04-22)
36. Visseren, FL, Mach, F, Smulders, YM, Carballo, D, Koskinas, KC, Bäck, M, et al. 2021 ESC guidelines on cardiovascular disease prevention in clinical practice: developed by the task force for cardiovascular disease prevention in clinical practice with representatives of the European Society of Cardiology and 12 medical societies with the special contribution of the European Association of Preventive Cardiology (EAPC). Eur J Prev Cardiol. (2022) 29:5–115. doi: 10.1093/eurjpc/zwab154
37. Whelton, PK, Carey, RM, Aronow, WS, Casey, DE, Collins, KJ, Dennison Himmelfarb, C, et al. 2017 ACC/AHA/AAPA/ABC/ACPM/AGS/APhA/ASH/ASPC/NMA/PCNA guideline for the prevention, detection, evaluation, and management of high blood pressure in adults: a report of the American College of Cardiology/American Heart Association task force on clinical practice guidelines. J Am Coll Cardiol. (2018) 71:e127–248. doi: 10.1016/j.jacc.2017.11.006
38. Volkert, D, Beck, AM, Cederholm, T, Cruz-Jentoft, A, Goisser, S, Hooper, L, et al. ESPEN guideline on clinical nutrition and hydration in geriatrics. Clin Nutr. (2019) 38:10–47. doi: 10.1016/j.clnu.2018.05.024
39. Williams, B, Mancia, G, Spiering, W, Agabiti Rosei, E, Azizi, M, Burnier, M, et al. 2018 ESC/ESH guidelines for the management of arterial hypertension: the task force for the management of arterial hypertension of the European Society of Cardiology (ESC) and the European Society of Hypertension (ESH). Eur Heart J. (2018) 39:3021–104. doi: 10.1093/eurheartj/ehy339
40. Kleindorfer, DO, Towfighi, A, Chaturvedi, S, Cockroft, KM, Gutierrez, J, Lombardi-Hill, D, et al. 2021 guideline for the prevention of stroke in patients with stroke and transient ischemic attack: a guideline from the American Heart Association/American Stroke Association. Stroke. (2021) 52:e364–467. doi: 10.1161/STR.0000000000000375
41. Gladstone, DJ, Lindsay, MP, Douketis, J, Smith, EE, Dowlatshahi, D, Wein, T, et al. Canadian stroke best practice recommendations: secondary prevention of stroke update 2020. Can J Neurol Sci. (2022) 49:315–37. doi: 10.1017/cjn.2021.127
42. National Institute for Health and Care Excellence. Chronic heart failure in adults: diagnosis and management. NICE guideline [NG106]. (2018). Available at: https://www.nice.org.uk/guidance/ng106 (Accessed 2024-04-22)
43. American Diabetes Association. 12. Older adults: standards of medical Care in Diabetes—2021. Diabetes Care. (2021) 44:S168–79. doi: 10.2337/dc21-S012
44. National Institute for Health and Care Excellence. Type 2 diabetes in adults: management. NICE guideline [NG28]. (2015). Available at: https://www.nice.org.uk/guidance/ng28 (Accessed 2024-04-22)
45. Karter, AJ, Warton, EM, Lipska, KJ, Ralston, JD, Moffet, HH, Jackson, GG, et al. Development and validation of a tool to identify patients with type 2 diabetes at high risk of hypoglycemia-related emergency department or hospital use. JAMA Intern Med. (2017) 177:1461–70. doi: 10.1001/jamainternmed.2017.3844
46. National Institute for Health and Care Excellence. Diabetic foot problems: prevention and management. NICE guideline [NG19]. (2015). Available at: https://www.nice.org.uk/guidance/ng19 (Accessed 2024-04-22).
47. National Institute for Health and Care Excellence. Chronic kidney disease: assessment and management. NICE guideline [NG203]. (2021). Available at: https://www.nice.org.uk/guidance/ng203 (Accessed 2024-04-22).
48. Ketteler, M, Block, GA, Evenepoel, P, Fukagawa, M, Herzog, CA, McCann, L, et al. Executive summary of the 2017 KDIGO chronic kidney disease–mineral and bone disorder (CKD-MBD) guideline update: what’s changed and why it matters. Kidney Int. (2017) 92:26–36. doi: 10.1016/j.kint.2017.04.006
49. Darryl Quarles, L, and Kendrick, J. Management of hyperphosphatemia in adults with chronic kidney disease. (2024) Available at: https://www.uptodate.com/contents/management-of-hyperphosphatemia-in-adults-with-chronic-kidney-disease#H1687951240 (Accessed 2024-04-22)
50. Johnson, KB, and FitzHenry, F. Case report: activity diagrams for integrating electronic prescribing tools into clinical workflow. J Am Med Inform Assoc. (2006) 13:391–5. doi: 10.1197/jamia.M2008
51. Spyrou, S., Bamidis, P., Pappas, K., and Maglaveras, N. (2005). Extending UML activity diagrams for workflow modelling with clinical documents in regional health information systems. Connecting Medical Informatics and Bioinformatics: Proceedings of the 19th Medical Informatics Europe Conference (MIE2005), Geneva, Switzerland. (pp. 1160–1165).
52. Carvalho, ECAD, Jayanti, MK, Batilana, AP, Kozan, AM, Rodrigues, MJ, Shah, J, et al. Standardizing clinical trials workflow representation in UML for international site comparison. PLoS One. (2010) 5:e13893. doi: 10.1371/journal.pone.0013893
53. HL7 FHIR® based secure data repository. onFHIR.io. (2020) Available at https://onfhir.io/ (Accessed 2024-04-22).
54. National Institute for Health and Care Excellence. Medicines adherence: involving patients in decisions about prescribed medicines and supporting adherence. Clinical guideline [CG76]. (2009). Available at: https://www.nice.org.uk/guidance/cg76 (Accessed 2024-04-22).
55. Gooch, P, and Roudsari, A. Computerization of workflows, guidelines, and care pathways: a review of implementation challenges for process-oriented health information systems. J Am Med Inform Assoc. (2011) 18:738–48. doi: 10.1136/amiajnl-2010-000033
56. Greenes, RA, Bates, DW, Kawamoto, K, Middleton, B, Osheroff, J, and Shahar, Y. Clinical decision support models and frameworks: seeking to address research issues underlying implementation successes and failures. J Biomed Inform. (2018) 78:134–43. doi: 10.1016/j.jbi.2017.12.005
57. Laka, M, Carter, D, Milazzo, A, and Merlin, T. Challenges and opportunities in implementing clinical decision support systems (CDSS) at scale: interviews with Australian policymakers. Health Policy Technol. (2022) 11:100652. doi: 10.1016/j.hlpt.2022.100652
58. Peart, A, Lewis, V, Barton, C, and Russell, G. Healthcare professionals providing care coordination to people living with multimorbidity: an interpretative phenomenological analysis. J Clin Nurs. (2020) 29:2317–28. doi: 10.1111/jocn.15243
Keywords: clinical decision support, clinical guideline, automation, integrated care, multimorbidity, dementia, HL7 FHIR
Citation: Gencturk M, Laleci Erturkmen GB, Akpinar AE, Pournik O, Ahmad B, Arvanitis TN, Schmidt-Barzynski W, Robbins T, Alcantud Corcoles R and Abizanda P (2024) Transforming evidence-based clinical guidelines into implementable clinical decision support services: the CAREPATH study for multimorbidity management. Front. Med. 11:1386689. doi: 10.3389/fmed.2024.1386689
Edited by:
Christine Gispen-de Wied, Gispen4RegulatoryScience, NetherlandsReviewed by:
Markus Wolfien, Technical University Dresden, GermanyManisha Mantri, Center for Development of Advanced Computing (C-DAC), India
Copyright © 2024 Gencturk, Laleci Erturkmen, Akpinar, Pournik, Ahmad, Arvanitis, Schmidt-Barzynski, Robbins, Alcantud Corcoles and Abizanda. This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY). The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.
*Correspondence: Mert Gencturk, bWVydEBzcmRjLmNvbS50cg==
†These authors have contributed equally to this work