<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Cancer</journal-id><journal-id journal-id-type="publisher-id">cancer</journal-id><journal-id journal-id-type="index">21</journal-id><journal-title>JMIR Cancer</journal-title><abbrev-journal-title>JMIR Cancer</abbrev-journal-title><issn pub-type="epub">2369-1999</issn><publisher><publisher-name>JMIR Publications</publisher-name><publisher-loc>Toronto, Canada</publisher-loc></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">v11i1e73691</article-id><article-id pub-id-type="doi">10.2196/73691</article-id><article-categories><subj-group subj-group-type="heading"><subject>Viewpoint</subject></subj-group></article-categories><title-group><article-title>DermaDashboard: Bridging the Gap Between FHIR Standards and Clinical Usability</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Borys</surname><given-names>Katarzyna</given-names></name><degrees>MSc</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Hartmann</surname><given-names>Eva Maria</given-names></name><degrees>MSc</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Idrissi-Yaghir</surname><given-names>Ahmad</given-names></name><degrees>MSc</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Livingstone</surname><given-names>Elisabeth</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Lodde</surname><given-names>Georg</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Schmidt</surname><given-names>Cynthia Sabrina</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff5">5</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Winnekens</surname><given-names>Philipp</given-names></name><degrees>MSc</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Friedrich</surname><given-names>Christoph M</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Hosch</surname><given-names>Ren&#x00E9;</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Nensa</surname><given-names>Felix</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib></contrib-group><aff id="aff1"><institution>Institute for Artificial Intelligence in Medicine, Essen University Hospital</institution><addr-line>Essen</addr-line><country>Germany</country></aff><aff id="aff2"><institution>Institute of Diagnostic and Interventional Radiology and Neuroradiology, Essen University Hospital</institution><addr-line>Hufelandstra&#x00DF;e 55</addr-line><addr-line>Essen</addr-line><country>Germany</country></aff><aff id="aff3"><institution>Department of Computer Science, University of Applied Sciences and Arts Dortmund</institution><addr-line>Dortmund</addr-line><country>Germany</country></aff><aff id="aff4"><institution>Department of Dermatology, Venereology, and Allergology, Essen University Hospital</institution><addr-line>Essen</addr-line><country>Germany</country></aff><aff id="aff5"><institution>Institute of Transfusion Medicine, Essen University Hospital</institution><addr-line>Essen</addr-line><country>Germany</country></aff><aff id="aff6"><institution>Institute for Medical Informatics, Biometry, and Epidemiology (IMIBE), Essen University Hospital</institution><addr-line>Essen</addr-line><country>Germany</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Cahill</surname><given-names>Naomi</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Gulden</surname><given-names>Christian</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Hu</surname><given-names>Paul Jen-Hwa</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Katarzyna Borys, MSc, Institute of Diagnostic and Interventional Radiology and Neuroradiology, Essen University Hospital, Hufelandstra&#x00DF;e 55, Essen, 45147, Germany, 49 201-723-77818; <email>katarzyna.borys@uk-essen.de</email></corresp><fn fn-type="equal" id="equal-contrib1"><label>*</label><p>these authors contributed equally</p></fn></author-notes><pub-date pub-type="collection"><year>2025</year></pub-date><pub-date pub-type="epub"><day>22</day><month>10</month><year>2025</year></pub-date><volume>11</volume><elocation-id>e73691</elocation-id><history><date date-type="received"><day>10</day><month>03</month><year>2025</year></date><date date-type="rev-recd"><day>18</day><month>08</month><year>2025</year></date><date date-type="accepted"><day>28</day><month>08</month><year>2025</year></date></history><copyright-statement>&#x00A9; Katarzyna Borys, Eva Maria Hartmann, Ahmad Idrissi-Yaghir, Elisabeth Livingstone, Georg Lodde, Cynthia Sabrina Schmidt, Philipp Winnekens, Christoph M Friedrich, Ren&#x00E9; Hosch, Felix Nensa. Originally published in JMIR Cancer (<ext-link ext-link-type="uri" xlink:href="https://cancer.jmir.org">https://cancer.jmir.org</ext-link>), 22.10.2025. </copyright-statement><copyright-year>2025</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Cancer, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://cancer.jmir.org/">https://cancer.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://cancer.jmir.org/2025/1/e73691"/><abstract><p>Over the past decade, Fast Healthcare Interoperability Resources (FHIR) have become increasingly relevant in health care data standardization. However, the complex structure of FHIR makes cohort analytics with many-to-many relations extremely time-consuming, and, impossible in many cases. To support exploratory cohort building and data visualization in oncology, especially for nontechnical users, we developed the DermaDashboard, an interactive dashboard built on top of a relational FHIR-compliant PostgreSQL database. Relevant oncology data was preaggregated with a materialized view, and the subsequent visualization layer was implemented using an open-source visualization tool, enabling clinicians to filter and analyze data without requiring familiarity with FHIR or SQL. The database encompassed data from 3949 patients with melanoma and included 82,783 health records. Core FHIR resources were Patient, DiagnosticReport, and QuestionnaireResponse, with 54 mapped attributes spanning demographics, stagings, mutations, and treatments. The resulting dashboard allowed filtering across 29 variables to construct subcohorts and generate aggregation analyses. This implementation shows how open interoperability data standards, such as FHIR, can be used in the development of modular, user-friendly clinical dashboards for cohort analysis, and the architecture demonstrates a feasible path toward democratizing access to structured health care data.</p></abstract><kwd-group><kwd>melanoma</kwd><kwd>dashboard</kwd><kwd>FHIR</kwd><kwd>data acquisition</kwd><kwd>interoperability</kwd><kwd>analytics</kwd><kwd>Fast Healthcare Interoperability Resources</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>In recent years, health care systems have rapidly embraced digitalization to enhance patient care, streamline clinical workflows, and improve interoperability of health information [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref4">4</xref>]. At the heart of this transformation is the widespread adoption of electronic health records (EHRs) [<xref ref-type="bibr" rid="ref5">5</xref>], which, on a broader scale, support the secondary use of data beyond clinical aspects, such as quality control, safety measurements, payments, certification, and research [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. However, hospitals employ diverse IT systems that store data in incompatible formats, thereby hindering cross-system analytics. The demand for interoperability among health care systems has thus become increasingly urgent. Among the technical standards driving this shift, the HL7 Fast Healthcare Interoperability Resources (FHIR) standard [<xref ref-type="bibr" rid="ref8">8</xref>] has emerged as a cornerstone for the structured, machine-readable exchange of health care data [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. By relying on modern web technologies, such as RESTful APIs (Representational State Transfer Application Programming Interfaces), FHIR enables scalable, modular data interoperability across diverse health care systems [<xref ref-type="bibr" rid="ref11">11</xref>-<xref ref-type="bibr" rid="ref13">13</xref>].</p><p>The application of FHIR in analytics and research, however, remains limited due to the standard&#x2019;s nested data structure. FHIR is a deeply nested graph, which is why analytics with many-to-many relationships require countless chained queries over the RESTful API. Because of this, analytics become slow and often impractical for advanced insights.</p><p>Additionally, most hospital information systems remain limited in scope, as they are primarily designed for viewing individual patient records. Consequently, they often lack functionalities for population-level analytics or cohort-based data exploration. Furthermore, raw EHR data is usually heterogeneous, incomplete, and multimodal [<xref ref-type="bibr" rid="ref14">14</xref>], making it difficult to query directly, especially for nontechnical users. These structural constraints hinder the ability to assemble complex patient cohorts and quickly extract statistics, capabilities that are essential for data-driven care and clinical research.</p><p>As health care institutions increasingly adopt FHIR to standardize data, there is a growing need for tools that enable accessible, exploratory analysis of FHIR-based datasets without requiring deep technical knowledge. In particular, there is an unmet need for lightweight, modular tools that can bridge the gap between the complex FHIR data standard and intuitive clinical interfaces used by health care professionals.</p><p>As a mitigating solution, we developed DermaDashboard, a proof-of-concept for a FHIR-based dashboard designed to facilitate exploratory cohort analysis for oncology research across multiple IT systems. Built using a commercial relational FHIR model and an open-source visualization tool, this dashboard enables structured cohort filtering, data summarization, and visual exploration. Demonstrated using patients with melanoma, the architecture is modular and generalizable to other diseases. This viewpoint provides a technical overview of the development pipeline, highlighting how FHIR-based data infrastructures can support the development of accessible, standards-driven dashboards in clinical environments.</p></sec><sec id="s2"><title>FHIR in Analytics: Challenges and Solutions</title><p>FHIR represents health care data as modular resources, each capturing specific clinical information which are linked via unique identifiers [<xref ref-type="bibr" rid="ref15">15</xref>]. While FHIR supports interoperability through RESTful APIs, assembling complex, multicriteria patient cohorts and performing cohort-level analyses can be challenging with conventional REST queries due to the hierarchical and deeply nested structure of the data [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>].</p><p>To address these practical challenges, our institution uses the relational FHIR engine provided by Firemetrics [<xref ref-type="bibr" rid="ref18">18</xref>], which stores FHIR resources in a relational PostgreSQL database without requiring custom mapping, maintaining full compliance with the FHIR standard. This relational representation allows preprocessing via SQL scripts to validate, clean, and normalize real-world clinical data, while also enabling efficient cohort-level queries and flexible integration with analytical dashboards. By combining the interoperability of FHIR with the performance and versatility of relational queries, the system supports facilitated data workflows.</p><p>Importantly, although our implementation uses Firemetrics [<xref ref-type="bibr" rid="ref18">18</xref>] for relational FHIR storage, the architectural approach is modular and not restricted to a single platform. It can be adapted to other systems that provide comparable functionality. For example, <italic>fhirbase</italic> [<xref ref-type="bibr" rid="ref19">19</xref>] provides a relational persistence layer for FHIR resources, while SQL-on-FHIR [<xref ref-type="bibr" rid="ref20">20</xref>] specifies a standard for expressing queries against FHIR data without prescribing a concrete implementation. In addition, FHIR servers such as Blaze [<xref ref-type="bibr" rid="ref21">21</xref>] offer an alternative infrastructure that can be extended with complementary components to support cohort-level querying and integration with analytical tools, thereby underscoring the flexibility and generalizability of the proposed framework.</p></sec><sec id="s3"><title>A Relational, Modular Approach to Clinical Data Integration</title><p>The first step of the pipeline is the assembly of a materialized view within the relational database. This materialized view serves as a precomputed layer that aggregates only the clinically relevant data from FHIR resources, specifically focusing on patients diagnosed with malignant melanoma and treated at the Department of Dermatology in the University Hospital Essen. Filtering needed data upfront reduces computational overhead and query times during downstream analyses. The construction of this view draws data from three primary FHIR resources:</p><list list-type="order"><list-item><p>Patient: providing demographic and identification data,</p></list-item><list-item><p>DiagnosticReport: containing structured clinical documentation, and</p></list-item><list-item><p>QuestionnaireResponse: holding detailed tumor documentation information in a structured but deeply nested format</p></list-item></list><p>Melanoma cases were identified by filtering the QuestionnaireResponse resource using standardized International Classification of Diseases (ICD)-10 German Modification [<xref ref-type="bibr" rid="ref22">22</xref>] codes (<italic>C43</italic>*). The initiation script of the materialized view (see code in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>) gathers each patient&#x2019;s demographic, diagnostic, histopathological, therapeutic, clinical, procedural, genetic, and consent information. The whole palette of required information for patients with melanoma was informed by interdisciplinary collaboration with dermatologists and prior research at our institution, which identified key data requirements for management of patients with melanoma via a dashboard, as shown by Hartmann et al [<xref ref-type="bibr" rid="ref23">23</xref>].</p><p>Due to the heterogeneous and semistructured nature of real-world hospital data, additional transformation steps were necessary to harmonize the data. These included standardizing inconsistent terminology, cleaning malformed or annotated values, parsing nonstandardized or missing datetime entries, and de-duplicating redundant records. These preprocessing steps were implemented during the initialization of the materialized view using a combination of SQL functions (eg, split_part, CASE) and JSONPath queries [<xref ref-type="bibr" rid="ref24">24</xref>], which enabled the extraction and modification of structured data from nested JSONB fields.</p></sec><sec id="s4"><title>Dashboard Design and Visualization</title><p>Using the FHIR resources <italic>Patient</italic>, <italic>DiagnosticReport</italic>, and <italic>QuestionnaireResponse</italic>, we assembled a dataset of 3949 patients with melanoma (47% female), comprising 82,783 records as of February 12, 2025. Multiple entries per patient document recurring clinical events, such as staging, therapies, surgeries, and side effects, capturing disease progression over time.</p><p>The visualization layer of <italic>DermaDashboard</italic> was implemented in Grafana (v9.5.3; Grafana Labs)[<xref ref-type="bibr" rid="ref25">25</xref>], which directly accesses the underlying database. As these queries deliver data in a usable format, no postprocessing is needed, enabling highly flexible ad-hoc analyses. Institutions with an existing FHIR server can replicate this open-source setup.</p><p>The central element of the dashboard is a configurable table (<xref ref-type="fig" rid="figure1">Figure 1</xref>) that integrates 54 data columns spanning demographics, diagnostics, histopathology, therapies, procedures, genetic information, and consent (see query in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>). Subpanels (<xref ref-type="fig" rid="figure2">Figures 2</xref> and <xref ref-type="fig" rid="figure3">3</xref>) provide instant cohort statistics (eg, age, sex, survival, ICD-10 codes, tumor subtypes, genetic mutations, procedures, therapy outcomes) and allow filtering by 29 clinical variables (see full description in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>). All panels update dynamically when filters are applied.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Outline of the Dashboard table panel: the main element of the Dashboard is the table panel, which presents all relevant patient information in tabular form. The presented outline displays deidentified patients, with a subset of columns focusing on demographics, therapy details, histological specifications, and mutation status.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="cancer_v11i1e73691_fig01.png"/></fig><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Outline of the dashboard&#x2019;s subpanels: subsequent panels provide analytic information about the defined cohort by presenting count metrics for tumor locations, histological subtypes, and genetic mutations. Furthermore, the distributions of survival in months, primary cases, ulceration statuses, and procedure types are displayed.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="cancer_v11i1e73691_fig02.png"/></fig><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>Annual analyses in the dashboard: specific panels focus on the annual analysis of performed surgical procedures and administered therapy protocols.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="cancer_v11i1e73691_fig03.png"/></fig><p>To facilitate analyses, Grafana supports a CSV export of defined cohorts. A custom deidentification variable removes names, dates, and identifiers before export. Finally, the dashboard is deployed securely in a locally hosted environment, ensuring compliance with institutional and legal data-protection standards.</p></sec><sec id="s5"><title>Barriers to Broader Adoption</title><p>While the modular dashboard pipeline we describe demonstrates the feasibility of FHIR-based analytics, broader adoption may be constrained by several practical factors. The complexity of FHIR&#x2019;s hierarchical and nested structure remains a challenge to widespread use, even as relational implementations offer promising alternatives. Our system addresses this by using a relational FHIR model and SQL-based transformations, but this approach requires domain-specific expertise that may not be readily available at all institutions.</p><p>Technical development and maintenance currently demand substantial internal knowledge of health care data. This reliance on specialized skills could limit replication, especially in smaller or less technically equipped settings. In its present form, the dashboard also focuses exclusively on structured data; its utility for unstructured data or multimodal integration remains unexplored.</p><p>Further, DermaDashboard has not yet undergone a formal clinical or usability evaluation. Its practical impact on workflows, decision-making, or outcomes has yet to be validated. Similarly, no comparative assessment has been conducted against other FHIR-based analytics tools or commercial dashboard platforms. These open questions merit exploration in future work, ideally using unified datasets and evaluation frameworks. Finally, the current system&#x2019;s focus on melanoma constrains immediate generalizability, though its architecture is designed to support broader use cases with minimal reconfiguration.</p></sec><sec id="s6" sec-type="conclusions"><title>Conclusion</title><p>The implementation of DermaDashboard presents a modular proof-of-concept for FHIR-based data analysis in a real-world clinical setting. Focused on melanoma, this pipeline addresses the challenge of translating complex health care data into a user-friendly format for downstream analysis and cohort acquisition, specifically for nontechnical users such as health care professionals. By combining diverse FHIR resources in a relational database and leveraging open-source visualization tools, the system enables accessible, reproducible cohort analysis tailored to institutional needs.</p><p>DermaDashboard showcases the practical utility of the FHIR standard by demonstrating how standardized, interoperable health care data can support user-friendly clinical tools. Its customizable filters, cohort-specific statistics, and CSV export functionality facilitate broad and flexible data access, especially to nontechnical users. The pipeline can be adapted to other disease domains through extended ICD code filtering and adjusted visualizations. While our implementation uses Firemetrics [<xref ref-type="bibr" rid="ref18">18</xref>] for relational FHIR storage, the underlying approach could be applied to other relational FHIR platforms or tools, such as SQL-on-FHIR [<xref ref-type="bibr" rid="ref20">20</xref>], fhirbase [<xref ref-type="bibr" rid="ref19">19</xref>], Blaze [<xref ref-type="bibr" rid="ref21">21</xref>], Grafana [<xref ref-type="bibr" rid="ref25">25</xref>], Metabase [<xref ref-type="bibr" rid="ref26">26</xref>], or Redash [<xref ref-type="bibr" rid="ref27">27</xref>], enabling replication across institutions with varying technical environments.</p><p>While FHIR adoption is expanding, its use often remains confined to narrow research applications. In oncological practice, where multimodal data is frequently siloed, dashboards like DermaDashboard could enhance informed decision-making and identify data quality issues.</p><p>By offering a flexible, standards-based framework, DermaDashboard contributes to operationalizing FHIR for routine care and highlights a scalable path forward for interoperable, clinician-accessible analytics in health care.</p></sec></body><back><fn-group><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">API</term><def><p>Application Programming Interfaces</p></def></def-item><def-item><term id="abb2">EHR</term><def><p>electronic health records</p></def></def-item><def-item><term id="abb3">FHIR</term><def><p>Fast Healthcare Interoperability Resources</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Stoumpos</surname><given-names>AI</given-names> </name><name name-style="western"><surname>Kitsios</surname><given-names>F</given-names> </name><name name-style="western"><surname>Talias</surname><given-names>MA</given-names> </name></person-group><article-title>Digital Transformation in Healthcare: Technology Acceptance and Its Applications</article-title><source>Int J Environ Res Public Health</source><year>2023</year><month>02</month><day>15</day><volume>20</volume><issue>4</issue><fpage>3407</fpage><pub-id pub-id-type="doi">10.3390/ijerph20043407</pub-id><pub-id pub-id-type="medline">36834105</pub-id></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Delice</surname><given-names>E</given-names> </name><name name-style="western"><surname>Polatl&#x0131;</surname><given-names>L&#x00D6;</given-names> </name><name name-style="western"><surname>Jbara</surname><given-names>KA</given-names> </name><name name-style="western"><surname>Tozan</surname><given-names>H</given-names> </name><name name-style="western"><surname>Ert&#x00FC;rk</surname><given-names>A</given-names> </name></person-group><article-title>Digitalization in healthcare: a systematic review of the literature</article-title><source>International Scientific Conference on Digital Transformation in Business</source><year>2023</year><volume>85</volume><issue>1</issue><fpage>26</fpage><pub-id pub-id-type="doi">10.3390/proceedings2023085026</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>S&#x00E6;tra</surname><given-names>HS</given-names> </name><name name-style="western"><surname>Fosch-Villaronga</surname><given-names>E</given-names> </name></person-group><article-title>Healthcare digitalisation and the changing nature of work and society</article-title><source>Healthcare (Basel)</source><year>2021</year><month>08</month><day>6</day><volume>9</volume><issue>8</issue><fpage>1007</fpage><pub-id pub-id-type="doi">10.3390/healthcare9081007</pub-id><pub-id pub-id-type="medline">34442144</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Saripalle</surname><given-names>R</given-names> </name><name name-style="western"><surname>Runyan</surname><given-names>C</given-names> </name><name name-style="western"><surname>Russell</surname><given-names>M</given-names> </name></person-group><article-title>Using HL7 FHIR to achieve interoperability in patient health record</article-title><source>J Biomed Inform</source><year>2019</year><month>06</month><volume>94</volume><fpage>103188</fpage><pub-id pub-id-type="doi">10.1016/j.jbi.2019.103188</pub-id><pub-id pub-id-type="medline">31063828</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Filice</surname><given-names>RW</given-names> </name><name name-style="western"><surname>Ratwani</surname><given-names>RM</given-names> </name></person-group><article-title>The case for user-centered artificial intelligence in radiology</article-title><source>Radiol Artif Intell</source><year>2020</year><month>05</month><volume>2</volume><issue>3</issue><fpage>e190095</fpage><pub-id pub-id-type="doi">10.1148/ryai.2020190095</pub-id><pub-id pub-id-type="medline">33937824</pub-id></nlm-citation></ref><ref id="ref6"><label>6</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ayaz</surname><given-names>M</given-names> </name><name name-style="western"><surname>Pasha</surname><given-names>MF</given-names> </name><name name-style="western"><surname>Alahmadi</surname><given-names>TJ</given-names> </name><name name-style="western"><surname>Abdullah</surname><given-names>NNB</given-names> </name><name name-style="western"><surname>Alkahtani</surname><given-names>HK</given-names> </name></person-group><article-title>Transforming healthcare analytics with FHIR: a framework for standardizing and analyzing clinical data</article-title><source>Healthcare (Basel)</source><year>2023</year><month>01</month><volume>11</volume><issue>12</issue><fpage>1729</fpage><pub-id pub-id-type="doi">10.3390/healthcare11121729</pub-id></nlm-citation></ref><ref id="ref7"><label>7</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Safran</surname><given-names>C</given-names> </name><name name-style="western"><surname>Bloomrosen</surname><given-names>M</given-names> </name><name name-style="western"><surname>Hammond</surname><given-names>WE</given-names> </name><etal/></person-group><article-title>Toward a national framework for the secondary use of health data: an American Medical Informatics Association White Paper</article-title><source>J Am Med Inform Assoc</source><year>2007</year><volume>14</volume><issue>1</issue><fpage>1</fpage><lpage>9</lpage><pub-id pub-id-type="doi">10.1197/jamia.M2273</pub-id><pub-id pub-id-type="medline">17077452</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Bender</surname><given-names>D</given-names> </name><name name-style="western"><surname>Sartipi</surname><given-names>K</given-names> </name></person-group><article-title>HL7 FHIR: an agile and restful approach to healthcare information exchange</article-title><conf-name>Proceedings of the 26th IEEE International Symposium on Computer-Based Medical Systems</conf-name><conf-date>Jun 20-22, 2013</conf-date><conf-loc>Porto, Portugal</conf-loc></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Duda</surname><given-names>SN</given-names> </name><name name-style="western"><surname>Kennedy</surname><given-names>N</given-names> </name><name name-style="western"><surname>Conway</surname><given-names>D</given-names> </name><etal/></person-group><article-title>HL7 FHIR-based tools and initiatives to support clinical research: a scoping review</article-title><source>J Am Med Inform Assoc</source><year>2022</year><month>08</month><day>16</day><volume>29</volume><issue>9</issue><fpage>1642</fpage><lpage>1653</lpage><pub-id pub-id-type="doi">10.1093/jamia/ocac105</pub-id><pub-id pub-id-type="medline">35818340</pub-id></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Vorisek</surname><given-names>CN</given-names> </name><name name-style="western"><surname>Lehne</surname><given-names>M</given-names> </name><name name-style="western"><surname>Klopfenstein</surname><given-names>SAI</given-names> </name><etal/></person-group><article-title>Fast Healthcare Interoperability Resources (FHIR) for Interoperability in health research: systematic review</article-title><source>JMIR Med Inform</source><year>2022</year><month>07</month><day>19</day><volume>10</volume><issue>7</issue><fpage>e35724</fpage><pub-id pub-id-type="doi">10.2196/35724</pub-id><pub-id pub-id-type="medline">35852842</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Mandl</surname><given-names>KD</given-names> </name><name name-style="western"><surname>Gottlieb</surname><given-names>D</given-names> </name><name name-style="western"><surname>Mandel</surname><given-names>JC</given-names> </name><etal/></person-group><article-title>Push Button Population Health: the SMART/HL7 FHIR Bulk Data Access Application Programming Interface</article-title><source>npj Digit Med</source><year>2020</year><month>11</month><day>19</day><volume>3</volume><issue>1</issue><fpage>1</fpage><lpage>9</lpage><pub-id pub-id-type="doi">10.1038/s41746-020-00358-4</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Griffin</surname><given-names>AC</given-names> </name><name name-style="western"><surname>He</surname><given-names>L</given-names> </name><name name-style="western"><surname>Sunjaya</surname><given-names>AP</given-names> </name><etal/></person-group><article-title>Clinical, technical, and implementation characteristics of real-world health applications using FHIR</article-title><source>JAMIA Open</source><year>2022</year><month>12</month><volume>5</volume><issue>4</issue><fpage>ooac077</fpage><pub-id pub-id-type="doi">10.1093/jamiaopen/ooac077</pub-id><pub-id pub-id-type="medline">36247086</pub-id></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lehne</surname><given-names>M</given-names> </name><name name-style="western"><surname>Luijten</surname><given-names>S</given-names> </name><name name-style="western"><surname>Vom Felde Genannt Imbusch</surname><given-names>P</given-names> </name><name name-style="western"><surname>Thun</surname><given-names>S</given-names> </name></person-group><article-title>The use of FHIR in digital health - a review of the scientific literature</article-title><source>Stud Health Technol Inform</source><year>2019</year><month>09</month><day>3</day><volume>267</volume><issue>52&#x2013;58</issue><fpage>52</fpage><lpage>58</lpage><pub-id pub-id-type="doi">10.3233/SHTI190805</pub-id><pub-id pub-id-type="medline">31483254</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Si</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Du</surname><given-names>J</given-names> </name><name name-style="western"><surname>Li</surname><given-names>Z</given-names> </name><etal/></person-group><article-title>Deep representation learning of patient data from Electronic Health Records (EHR): a systematic review</article-title><source>J Biomed Inform</source><year>2021</year><month>03</month><volume>115</volume><fpage>103671</fpage><pub-id pub-id-type="doi">10.1016/j.jbi.2020.103671</pub-id><pub-id pub-id-type="medline">33387683</pub-id></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="web"><article-title>Resourcelist - FHIR v500</article-title><source>HL7FHIR</source><access-date>2025-02-12</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.hl7.org/fhir/resourcelist.html">https://www.hl7.org/fhir/resourcelist.html</ext-link></comment></nlm-citation></ref><ref id="ref16"><label>16</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ayaz</surname><given-names>M</given-names> </name><name name-style="western"><surname>Pasha</surname><given-names>MF</given-names> </name><name name-style="western"><surname>Alzahrani</surname><given-names>MY</given-names> </name><name name-style="western"><surname>Budiarto</surname><given-names>R</given-names> </name><name name-style="western"><surname>Stiawan</surname><given-names>D</given-names> </name></person-group><article-title>The Fast Health Interoperability Resources (FHIR) Standard: systematic literature review of implementations, applications, challenges and opportunities</article-title><source>JMIR Med Inform</source><year>2021</year><month>07</month><day>30</day><volume>9</volume><issue>7</issue><fpage>e21929</fpage><pub-id pub-id-type="doi">10.2196/21929</pub-id><pub-id pub-id-type="medline">34328424</pub-id></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tabari</surname><given-names>P</given-names> </name><name name-style="western"><surname>Costagliola</surname><given-names>G</given-names> </name><name name-style="western"><surname>De Rosa</surname><given-names>M</given-names> </name><name name-style="western"><surname>Boeker</surname><given-names>M</given-names> </name></person-group><article-title>State-of-the-Art Fast Healthcare Interoperability Resources (FHIR)-based data model and structure implementations: systematic scoping review</article-title><source>JMIR Med Inform</source><year>2024</year><month>09</month><day>24</day><volume>12</volume><issue>1</issue><fpage>e58445</fpage><pub-id pub-id-type="doi">10.2196/58445</pub-id><pub-id pub-id-type="medline">39316433</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="web"><article-title>Firemetrics gmbh | interoperabilit&#x00E4;t</article-title><source>Firemetrics GmbH</source><access-date>2025-02-12</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.firemetricshealth.com">https://www.firemetricshealth.com</ext-link></comment></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="web"><article-title>Fhirbase/fhirbase</article-title><source>Fhirbase</source><year>2025</year><access-date>2025-05-28</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://github.com/fhirbase/fhirbase">https://github.com/fhirbase/fhirbase</ext-link></comment></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="web"><article-title>FHIR/sql-on-FHIR-v2</article-title><source>FHIR</source><year>2025</year><access-date>2025-05-28</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://github.com/FHIR/sql-on-fhir-v2">https://github.com/FHIR/sql-on-fhir-v2</ext-link></comment></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="web"><article-title>Samply/blaze</article-title><source>Samply</source><year>2025</year><access-date>2025-05-28</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://github.com/samply/blaze">https://github.com/samply/blaze</ext-link></comment></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="web"><source>BfArM - ICD-10-GM</source><access-date>2025-05-14</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.bfarm.de/EN/Code-systems/Classifications/ICD/ICD-10-GM/_node.html">https://www.bfarm.de/EN/Code-systems/Classifications/ICD/ICD-10-GM/_node.html</ext-link></comment></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hartmann</surname><given-names>EM</given-names> </name><name name-style="western"><surname>K&#x00FC;per</surname><given-names>A</given-names> </name><name name-style="western"><surname>Swoboda</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Requirements for a dashboard optimized for melanoma patient care through user-centered context exploration</article-title><source>Sci Rep</source><year>2024</year><month>07</month><day>29</day><volume>14</volume><issue>1</issue><fpage>17471</fpage><pub-id pub-id-type="doi">10.1038/s41598-024-67857-2</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="web"><source>JSONPath - XPath for JSON</source><access-date>2025-05-28</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://goessner.net/articles/JsonPath/">https://goessner.net/articles/JsonPath/</ext-link></comment></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="web"><article-title>Grafana: the open and composable observability platform</article-title><source>Grafana Labs</source><access-date>2025-02-12</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://grafana.com/">https://grafana.com/</ext-link></comment></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="web"><source>Open source business intelligence, dashboards, and data visualizations | Metabase</source><access-date>2025-06-23</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.metabase.com/">https://www.metabase.com/</ext-link></comment></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="web"><source>Redash helps you make sense of your data</source><access-date>2025-06-23</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://redash.io/">https://redash.io/</ext-link></comment></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>SQL query used to initialize the materialized view for FHIR-based melanoma cohort preaggregation.</p><media xlink:href="cancer_v11i1e73691_app1.txt" xlink:title="TXT File, 8 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>SQL query constructed within Grafana to retrieve data from the FHIR-based materialized view.</p><media xlink:href="cancer_v11i1e73691_app2.txt" xlink:title="TXT File, 7 KB"/></supplementary-material><supplementary-material id="app3"><label>Multimedia Appendix 3</label><p>Overview of Grafana table panel column names, descriptions, and defined filtering variables.</p><media xlink:href="cancer_v11i1e73691_app3.docx" xlink:title="DOCX File, 224 KB"/></supplementary-material></app-group></back></article>