<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">FAIR Software as a Service: Combining tools to implement FAIR for clinical data platforms</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Rick</forename><surname>Overkleeft</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Nederland B.V</orgName>
								<address>
									<addrLine>4MedBox, Kanaalpark 157</addrLine>
									<postCode>2321 JW</postCode>
									<settlement>Leiden</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">Leiden University Medical Center</orgName>
								<address>
									<addrLine>Albinusdreef 2</addrLine>
									<postCode>2333 ZA</postCode>
									<settlement>Leiden</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Sander</forename><surname>Van Boom</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Nederland B.V</orgName>
								<address>
									<addrLine>4MedBox, Kanaalpark 157</addrLine>
									<postCode>2321 JW</postCode>
									<settlement>Leiden</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">Leiden University Medical Center</orgName>
								<address>
									<addrLine>Albinusdreef 2</addrLine>
									<postCode>2333 ZA</postCode>
									<settlement>Leiden</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Eric</forename><surname>Prud'hommeaux</surname></persName>
							<affiliation key="aff2">
								<orgName type="department">Janeiro Digital</orgName>
								<address>
									<addrLine>2 rue nouvelle de Wailly</addrLine>
									<postCode>63000</postCode>
									<settlement>Clermont-Ferrand</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Kees</forename><surname>Burger</surname></persName>
							<affiliation key="aff3">
								<orgName type="department">Health-RI</orgName>
								<address>
									<settlement>Utrecht</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Jip</forename><surname>Fransen</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">Leiden University Medical Center</orgName>
								<address>
									<addrLine>Albinusdreef 2</addrLine>
									<postCode>2333 ZA</postCode>
									<settlement>Leiden</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Teus</forename><surname>Kappen</surname></persName>
							<affiliation key="aff4">
								<orgName type="institution">Universitair Medisch Centrum Utrecht</orgName>
								<address>
									<settlement>Utrecht</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Luiz</forename><surname>Bonino</surname></persName>
						</author>
						<author>
							<persName><forename type="first">Silva</forename><surname>Santos</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">Leiden University Medical Center</orgName>
								<address>
									<addrLine>Albinusdreef 2</addrLine>
									<postCode>2333 ZA</postCode>
									<settlement>Leiden</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
							<affiliation key="aff5">
								<orgName type="institution">Technical University Twente</orgName>
								<address>
									<settlement>Enschede</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Rajaram</forename><surname>Kaliyaperumal</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">Leiden University Medical Center</orgName>
								<address>
									<addrLine>Albinusdreef 2</addrLine>
									<postCode>2333 ZA</postCode>
									<settlement>Leiden</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
						<author role="corresp">
							<persName><forename type="first">Marco</forename><surname>Roos</surname></persName>
							<email>m.roos@lumc.nl</email>
							<affiliation key="aff1">
								<orgName type="institution">Leiden University Medical Center</orgName>
								<address>
									<addrLine>Albinusdreef 2</addrLine>
									<postCode>2333 ZA</postCode>
									<settlement>Leiden</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff6">
								<orgName type="institution">Rajaram Kaliyaperumal</orgName>
								<address>
									<addrLine>Marco Roos, 02-01</addrLine>
									<postCode>2024</postCode>
									<settlement>Leiden</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">FAIR Software as a Service: Combining tools to implement FAIR for clinical data platforms</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">EA0F81233A06B44145D5D028949FE8FE</idno>
					<idno type="DOI">10.1162/dint_a_00160</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T17:40+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>FAIR</term>
					<term>implementation</term>
					<term>architecture</term>
					<term>FAIR Data Point</term>
					<term>SaaS</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Many DCCs have operational expertise in deploying software services, but lack expertise in deploying and exploiting FAIR services that use Semantic Web technology for machine actionability. Although local deployment is lightweight and non-invasive for institutional infrastructure, engineers are not yet familiar with the underlying web technologies of FAIR services. This poses a risk for delivering the FAIR foundation of a federated health data infrastructure that is ready for federated analytics, AI, and machine learning. This project is making deployment by institutional DCCs of FAIR services cost-effective, scalable, and sustainable by delivering 'FAIR Software as a Service' (FAIR-SaaS).</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>Semantic Web (SW) technology is a common implementation choice for software services that help meet the machine actionability requirement of the FAIR principles. An example is the DCAT-based FAIR Data Point (FDP) <ref type="bibr" target="#b0">[1]</ref>. Although local deployment is lightweight for SW experts and noninvasive for institutional infrastructure, adoption is hampered if engineers are not yet familiar with the underlying technologies of FAIR services. IT departments and Data Competency Centres (DCCs) usually have operational expertise in deploying software services as such, but lack expertise in using Semantic Web technology. This poses a risk for delivering the FAIR foundation of a federated health data infrastructure that is ready for federated analytics, AI, and machine learning.</p><p>We present our first results of a project that aims to make deployment of FAIR services by institutional DCCs cost-effective, scalable, and sustainable by delivering 'FAIR Software as a Service' (FAIR-SaaS). FAIR-SaaS is centrally hosted software that is preconfigured and updated by FAIR specialists for institutional DCCs. The project starts with (i) common FAIR Data Point (FDP) 2 configurations that DCCs can deploy to describe their resources for machines, (ii) grlc-inspired configurations facilitating DCCs to generate common APIs from FAIR metadata.</p><p>An early target is to simplify the processes for DCCs to contribute FDPs for data and compute capacity to the Dutch national health infrastructure, and comply with multiple existing and future common APIs. FAIR SaaS are straightforward to update for FAIR experts (e.g. grlc SaaS requires simple queries on FAIR metadata) who can guarantee convergence to international standards. The hypothesis is that FAIR SaaS provided by SURF, the Dutch national hosting organisation, which requires a minimal number of Semantic Web experts for maintenance, has a significant impact on the applicability, scalability, and sustainability of a health data infrastructure, demonstrating how a critical mass of FAIR (meta)data can be achieved for enhancing health care and life sciences.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">From concept to development</head><p>A use-case has been defined with local health data project leaders from the LUMC, UMC Utrecht and Erasmus MC, to develop the overall architecture and concept of the service:</p><p>As a cardiologist I would like to see information on physical fitness (weight, stamina, blood pressure, etc.) for patients planned for thorax surgery across two hospitals, such that I can screen patients based on their physical fitness for surgery and take decisions on timing of surgery and capacity planning. Patients that are not selected must undergo a fitness program.</p><p>The use-case was used to create the business architecture that has been defined in Figure <ref type="figure" target="#fig_0">1</ref>, which resulted in the application architecture defined in Figure <ref type="figure" target="#fig_1">2</ref>. From a FAIR mindset, we have defined that these services do not need to be created by us but should be re-used where available and adjusted if necessary.</p><p>To lower the amount of knowledge about Semantic Web technology needed by IT personnel we concluded that the first services will be delivered in a docker container and that we need to set up a Virtual Machine (VM) image with these dockers pre-installed. The VM is optional if docker knowledge is present at the specific IT department. We are currently combining existing tools to develop these features.  </p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 FAIR</head><label>1</label><figDesc>Figure 1 FAIR-SaaS Business architecture, a conceptual overview of the need by the experts.</figDesc><graphic coords="2,278.10,256.53,244.90,156.95" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2</head><label>2</label><figDesc>Figure 2 FAIR-SaaS Application architecture, a conceptual overview of the software services that are needed to address the need of the experts.</figDesc><graphic coords="2,283.20,436.07,239.28,119.35" type="bitmap" /></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Acknowledgements</head><p>We acknowledge SURF and NWO for support and funding, Health RI, the European Joint Programme Rare Diseases and EOSC-Life for developments leading to this project (H2020 N°82557, 824087).</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">FAIR Data Point: A FAIR-Oriented Approach for Metadata Publication</title>
		<author>
			<persName><forename type="first">Luiz</forename><surname>Olavo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Bonino</forename><surname>Da</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Silva</forename><surname>Santos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Kees</forename><surname>Burger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Rajaram</forename><surname>Kaliyaperumal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Mark</forename><forename type="middle">D</forename><surname>Wilkinson</surname></persName>
		</author>
		<idno type="DOI">10.1162/dint_a_00160</idno>
		<idno>doi:</idno>
		<ptr target="https://doi.org/10.1162/dint_a_00160" />
	</analytic>
	<monogr>
		<title level="j">Data Intelligence</title>
		<imprint>
			<biblScope unit="volume">5</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="163" to="183" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
