This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.
Clinical decision support (CDS) can improve health care with respect to the quality of care, patient safety, efficiency, and effectiveness. Establishing a CDS system in a health care setting remains a challenge. A few hospitals have used self-developed in-house CDS systems or commercial CDS solutions. Since these in-house CDS systems tend to be tightly coupled with a specific electronic health record system, the functionality and knowledge base are not easily shareable. A shared interoperable CDS system facilitates the sharing of the knowledge base and extension of CDS services.
The study focuses on developing and deploying the national CDS service for the drug-allergy interaction (DAI) check for health care providers in Korea that need to introduce the service but lack the budget and expertise.
To provide the shared interoperable CDS service, we designed and implemented the system based on the CDS Hooks specification and Health Level Seven (HL7) Fast Healthcare Interoperability Resources (FHIR) standard. The study describes the CDS development process. The system development went through requirement analysis, design, implementation, and deployment. In particular, the concept architecture was designed based on the CDS Hooks structure. The MedicationRequest and AllergyIntolerance resources were profiled to exchange data using the FHIR standard. The discovery and DAI check application programming interfaces and rule engine were developed.
The CDS service was deployed on G-Cloud, a government cloud service. In March 2021, the CDS service was launched, and 67 health care providers participated in the CDS service. The health care providers participated in the service with 1,008,357 DAI checks for 114,694 patients, of which 33,054 (3.32%) cases resulted in a “warning.”
Korea’s Ministry of Health and Welfare has been trying to build an HL7 FHIR-based ecosystem in Korea. As one of these efforts, the CDS service initiative has been conducted. To promote the rapid adoption of the HL7 FHIR standard, it is necessary to accelerate practical service development and to appeal to policy makers regarding the benefits of FHIR standardization. With the development of various case-specific implementation guides using the Korea Core implementation guide, the FHIR standards will be distributed nationwide, and more shared interoperable health care services will be introduced in Korea.
Clinical decision support (CDS) can improve health care with respect to the quality of care, patient safety, efficiency, and effectiveness [
However, adopting a CDS system in a health care setting remains a challenge [
Shared interoperable CDS services that enable sharing the knowledge base and expansion of the CDS service can mitigate the previous problems. The services can be implemented using the CDS Hooks, that is, Health Level Seven (HL7) International–published specifications for CDS [
Since 2011, the Health Insurance Review and Assessment Service (HIRA) in Korea has provided the drug utilization review (DUR) program as a CDS system containing real-time drug safety data for doctors and pharmacists. The DUR program presents 11 review items, including drug-drug interactions, duplicate prescriptions, and drug regimen dose and duration. The DUR system has been distributed among over 99.8% of health care providers as of 2019 [
Korea’s Ministry of Health and Welfare (MoHW) oversees several national initiatives to apply and distribute interoperable health IT standards. As one of several national initiatives, feasibility studies are ongoing to embrace the HL7 FHIR standards [
In this study, we focus on developing and deploying the sharable and interoperable CDS service for the drug-allergy interaction (DAI) check based on the CDS Hooks specification at the national level. The main objective of CDS service in the initial stage is technical feasibility and service availability. The DUR program in Korea does not cover the DAI check due to low awareness of the social burden and its prevention for the DAI when setting the review items in 2011 [
We developed a shared interoperable CDS system based on CDS Hooks for a DAI check to provide a service to health care providers. The system is triggered by medication orders in the EHR system. When it is evoked, the system checks the DAI and returns recommendations back to the provider. We developed the system in the following steps: (1) requirement analysis, (2) design, (3) implementation, and (4) deployment. In the first step, we identified data elements used for DAI check and classified them into mandatory and optional. We also selected the FHIR resources for contextual information available within an EHR system. Second, we designed concept architecture and web service end points, representational state transfer (RESTful) application programming interfaces (APIs), based on the CDS Hooks structure. We profiled FHIR resources according to data elements and specified the card, a form that represented a result of decision support. We designed a rule engine including a four-step drug-allergy screening logic and knowledge base. Lastly, we implemented components and functions, and deployed the CDS system on a government-managed cloud service called G-Cloud.
The CDS service can simultaneously be used by multiple health care providers, such as tertiary hospitals, small- to medium-sized hospitals, and clinics with their own EHR systems. Health care providers can DAI check using a remote CDS service call when ordering medications. An EHR system creates a request payload with patients’ prescriptions and allergy data, and transmits it to the CDS service. The CDS service executes the DAI check logic using the request payload and then returns the result to the EHR system.
We designed a concept architecture according to the CDS Hooks structure, which consists of CDS services, CDS clients, and cards, as shown in
The CDS service was designed as a cloud service and consisted of an interface engine, rule engine, authentication and authorization server, and audit trail. The interface engine has three components: the service gateway, the FHIR resource parser, and the CDS Hooks card generator. The service gateway provides a discovery end point and DAI check end point, and the FHIR resource parser parses request payload data to relay to the rule engine. The CDS Hooks card generator creates decision support results as a card to return to the CDS client. The rule engine checks the DAI using the prescription and patients’ allergy information and then returns a result of allergy screening to the CDS Hooks card generator. The authenticate and authorization server authenticates the EHR system using an issued token, and the audit trail monitors which health care providers invoke the service and when and how often they use it.
We applied the CDS Hooks security model with some variations to the CDS service. The CDS Hooks specification provides a security model, such as mutual identification, transport layer security protocol, and JSON web token. We developed the authentication and authorization server to provide a token to CDS clients. The token issued by the CDS service authenticates the CDS client. It reduces the burden on the health care provider’s authentication server development and helps a wider adoption of the CDS service. In addition, a whitelist of health care providers is managed based on our risk management strategy.
The CDS client creates an HTTP request to the CDS Hooks service with parameters that include required fields (hook, hookInstance, and context) and optional fields (fhirServer, fhirAuthorization, and prefetch). The context and prefetch fields have the FHIR resources, which are translated by the FHIR adapter. The FHIR adapter was considered instead of an FHIR server since the adoption of the FHIR standard is in its infancy in Korea.
The concept architecture for the shared interoperable CDS system is based on CDS Hooks anatomy. Multiple health care providers simultaneously invoke the shared interoperable CDS service deployed on G-Cloud using a hook and receive a card as a response. CDS: clinical decision support; EHR: electronic health record; FHIR: Fast Healthcare Interoperability Resources.
We identified data elements for the DAI check and profiled two FHIR resources, MedicationRequest and AllergyIntolerance, based on the FHIR R4 (v4.0.1) [
The AllergyIntolerance resource represents a record of a clinical assessment of an allergy or intolerance, as shown in
The cardinality constraints of the AllergyIntolerance resource are inherited by the KR Core IG. The identifier, category, and code elements are marked as “must support.” The profiled resources are published to SIMPLIFIER.NET, one of the FHIR registries.
Two profiled resources are conformant to the KR Core IG in
The MedicationRequest and AllergyIntolerance resource profile. The resources profiled for the clinical decision support service are inherited from the Korea Core Implementation Guide 1.0.0. Elements with "must support" are marked with an "S" in the red square.
The MedicationRequest and AllergyIntolerance resources profiled through the shared interoperable clinical decision support system are conformed with the KR Core MedicationRequest profile and KR Core AllergyIntolerance profile. FHIR: Fast Healthcare Interoperability; HL7: Health Level Seven; KR: Korea.
Two end points were designed and implemented: the discovery and DAI check APIs. The discovery API provides the list of CDS services, including a description of the CDS service and any requested data to be prefetched [
The CDS service responds to the CDS client with cards containing information, suggested actions, and links to launch an application. The DAI check API returns a card with a “warning” indicator, as shown in
Examples of order-sign hook and warning card. The order-sign hook has userId, patientId, and draftOrders as required fields, but userId is not used in the clinical decision support (CDS) service for the drug-allergy interaction (DAI) check. The card, the response of the CDS service, includes the results of the DAI check, suggested actions, and links to the launch app.
We designed and developed the rule engine to check an interaction between a patient’s medication allergens and prescribed medications transmitted from a health care provider, as shown in
The Drug Allergy database consists of master and relation tables. The master tables are the Drug, Drug Class, Ingredient, and Cross-Reactive Allergen. The Drug and Drug Class tables uniquely identify regulated medicinal products using the KD code as the primary key. The Ingredient table models substances that constitute a medicinal product and includes columns such as ingredient code, name, and synonym. These tables are designed based on the Identification of Medicinal Products, a suite of five International Organization for Standardization standards to facilitate the reliable exchange of medicinal product information. The Ingredient table is related to the Cross-Reactive, Drug, and Drug Class tables by each primary key. In addition to these tables, the drug allergy database has several relation tables used to perform DAI checks.
The three-step drug-allergy interaction check screening process: (1) check whether allergens and prescribed medications have the same product or ingredient, (2) check whether they belong to the same drug or ingredient class, and (3) check whether they have cross-reactive allergens. KD: Korea Drug.
This study did not require ethics approval as no personal data was collected, and no interventions were implemented.
In this study, the national CDS service for the DAI check was developed to ensure the safe use of medicine and was deployed on G-Cloud, a government cloud service established and run by National Computing and Information Service in Korea [
Physicians use the national CDS service for the DAI checks when prescribing medications. The physicians should search the allergen codes provided by the CDS service before calling the CDS service. Since Korea does not yet have a national standard allergy code system, most health care providers store allergy data for the patient as text. To use the CDS service, physicians are also expected to search for an allergy code in the proprietary value set. For this extra step, the CDS service IG provides a reference implementation to inquire about the allergen, allergic reaction, and severity codes, as shown in
Results of the shared interoperable CDS service for drug-allergy interaction check in December 2021.
Result category | Amount | |
|
||
|
Health care providers | 67 |
|
Patients | 114,694 |
|
||
|
Drug-allergy interaction checks | 1,008,357 |
|
||
|
Warning cards | 33,504 (3.32) |
|
No responses | 974,853 (96.68) |
aCDS: clinical decision support.
Screenshot of the reference implementation for a patient’s allergen inquiry. To drug-allergy interaction check, physicians should retrieve a patient's allergen code through reference implementation provided by the clincal decision support service.
The study applied the CDS Hooks specification to provide the nationwide shared interoperable CDS service for the DAI check. The CDS service has been deployed on G-Cloud, and all authorized health care providers can use the service simultaneously through RESTful APIs. As of December 2021, 67 health care providers have participated in the initiative. Since the service developed in this study conforms with the CDS Hooks specification, clinical knowledge bases can be shared, and the services can be scalable.
According to the CDS service results report, the rate of warnings that occurred among the CDS service was 7.74% from 29 of the 67 participating hospitals for 1610 patients from May to August 2021. Among the warnings, the most frequent was the cross-reactive allergen check (43.55%), followed by the same drug or ingredient class check (28.77%) and the same product or ingredient check (27.68%). After warning responses from the CDS service, 9.07% of prescriptions were changed, and 90.93% were not changed [
We designed the CDS system based on serverless FHIR architecture. A CDS service can request additional data regarding the clinical workflow context to the FHIR server at providers via the hook parameters in the CDS Hooks specification. In Korea, the adoption of FHIR standards is in its infancy, and few health care providers have FHIR servers for requesting any additional data. Thus, we applied serverless FHIR architecture, identified the required data in advance, and assigned it in the prefetch field.
As awareness of national allergy codes increases, the MoHW of Korea is developing a national allergy code system. The KR Core AllergyIntolerance profile binds the KR Core AllergyIntolerance Code value set, a renamed version of the AllergyIntolerance Substance value set defined in the FHIR R4. The binding strength of the two value sets is preferred. It is meant to encourage drawing from the specified codes, but it is not required. Currently, there is no national allergy code system available in Korea, and the KR Core AllergyIntolerance Code value set is basically a placeholder for future value set development. Due to the lack of a national allergy code system, we chose to use a proprietary value set. When the national allergy code system is developed, it will replace the value set to draw from the national allergy code system with binding strength required, as well as the KR Core AllergyIntolerance Code value set.
The shared interoperable CDS service for the DAI check based on the CDS Hooks was developed and deployed. The CDS service is currently provided to 67 health care providers. The MoHW has been making efforts to build the HL7 FHIR-based ecosystem in Korea. As one of these efforts, the CDS service initiative was conducted. To promote the rapid adoption of the HL7 FHIR standards, it is necessary to accelerate the practical service development and appeal the benefits of FHIR-based standardization to policy makers; this is the primary purpose of guiding the CDS service. Lastly, with the development of various case-specific IGs based on the KR Core IG, the FHIR standards will be distributed to the health IT industry, and more shared interoperable health care services will be introduced in Korea.
application programming interface
clinical decision support
drug-allergy interaction
drug utilization review
electronic health record
Fast Healthcare Interoperability Resources
Health Insurance Review and Assessment Service
Health Level Seven
implementation guide
Korea Drug
Korea
Ministry of Health and Welfare
representational state transfer
Substitutable Medical Applications, Reusable Technologies
This work was supported by the Industrial Strategic Technology Development Program (grant 20020743) funded by the Ministry of Trade, Industry & Energy, Republic of Korea.
None declared.