## 5 Use Case
\begin{table}
\begin{tabular}{c c c} \hline \hline
**EHR Augmentation** & **EOI** & **EOI Coded Value** & **EOI Binding Triple** \\ \hline Drug-drug interactions & patient’s active medication & _Filgrastim-[SNOMED-CT:386948008]_ & _<[[http://www.w3.org/2004/02/skos/core#_](http://www.w3.org/2004/02/skos/core#_)]([http://www.w3.org/2004/02/skos/core#_](http://www.w3.org/2004/02/skos/core#_)) \\  & & _exactMatch_ & _<[[http://bio2.df.org/drugbank:DB00099](http://bio2.df.org/drugbank:DB00099)]([http://bio2.df.org/drugbank:DB00099](http://bio2.df.org/drugbank:DB00099))>_ \\  & & & _<[[http://purl.bioontology.org/ontology/_](http://purl.bioontology.org/ontology/_)]([http://purl.bioontology.org/ontology/_](http://purl.bioontology.org/ontology/_)) \\ Disease-related treatments & active episodes of patient’s diseases & _Alzheimer-[SNOMED-CT:26929004]_ & _<[[http://www.w3.org/2004/02/skos/core#_](http://www.w3.org/2004/02/skos/core#_)]([http://www.w3.org/2004/02/skos/core#_](http://www.w3.org/2004/02/skos/core#_)) \\  & & & _<[[http://purl.bioontology.org/ontology/_](http://purl.bioontology.org/ontology/_)]([http://purl.bioontology.org/ontology/_](http://purl.bioontology.org/ontology/_)) \\  & & & _NDFRT_/N0000000363>_ \\ \hline \hline \end{tabular}
\end{table} 
Table 3: EOI binding triples generated for each EHR augmentation taking the initial EHR extract introduced in Figure 10 and the arguments described in Tables 1 and 2, respectively. \begin{table}
\begin{tabular}{c c c} \hline \hline
**Variable** & **Value** \\ \hline Initial EHR Extract & \multicolumn{2}{c}{An instance of the summary EHR archetype provided at runtime} \\  & & _/content[archetype\_id=“at0043”]_ \\ Inputs & \multicolumn{2}{c}{_/members[archetype\_id=“at0042”]_} \\  & Path to the EOI in the initial EHR archetype & \multicolumn{2}{c}{_/members[archetype\_id=“at0046”]_} \\  & & _/items[archetype\_id=“at0158”]_/value_ \\  & The predicate URL & _[[http://www.w3.org/2004/02/skos/core#_exactMatch_](http://www.w3.org/2004/02/skos/core#_exactMatch_)]([http://www.w3.org/2004/02/skos/core#_exactMatch_](http://www.w3.org/2004/02/skos/core#_exactMatch_)) \\  & The name of the source terminology employed by the & _SNOMEDCT_ \\  & EOI coded values & _[[http://purl.bioontology.org/ontology/NDFRT_](http://purl.bioontology.org/ontology/NDFRT_)]([http://purl.bioontology.org/ontology/NDFRT_](http://purl.bioontology.org/ontology/NDFRT_)) \\  & The identifier URL of the target terminology/ontology & _[[http://purl.bioontology.org/ontology/NDFRT_](http://purl.bioontology.org/ontology/NDFRT_)]([http://purl.bioontology.org/ontology/NDFRT_](http://purl.bioontology.org/ontology/NDFRT_)) \\  & returned by the terminology mapping service & _[[http://purl.bioontology.org/ontology/NDFRT_](http://purl.bioontology.org/ontology/NDFRT_)]([http://purl.bioontology.org/ontology/NDFRT_](http://purl.bioontology.org/ontology/NDFRT_)) \\  & The URL prefix of data items in the target dataset & RDF triples that relates EOIs from the initial EHR extract \\ Output & The EOI binding triples & with data items in the target dataset \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Inputs and output of the automatic procedure to build the EOI binding triples for the disease-related treatments’ EHR augmentation. Figure 13 shows the augmented archetype _CEN-EN13606-COMPOSITION_. _Historia-ClinicaResumidaAugmented.v1_, which results from combining the augmentation archetypes and the initial EHR archetype. LinkEHR was used to model the required archetypes, and to define the mapping relationships for these archetypes and their respective sources. Table 4 establishes the mappings carried out to define the augmented summary EHR. Note that the only archetype existing before the definition of an augmented EHR is the initial EHR archetype (_CEN-EN13606-COMPOSITION.HistoriaClinicaResumida.v1_). The  
Figure 11: SPARQL queries to obtain the augmentation contents. (**a**) The query to collect the drug–drug interactions.