## 5 Use Case
This retrieves interaction descriptions, codes, and names of the drugs involved in each drug–drug interaction. (**b**) The query to retrieve disease-related treatments. This obtains treatments and descriptions related to a given disease. In both cases, queries are parametrized using the EOI binding triples as part of the query graph, and the _skos:exactMatch_ predicate allows filtering the augmentation content by retrieving only the information related to the coded values of the EOI binding triples. Figure 12: Augmentation archetypes’ visualization from LinkEHR. (**a**) The _CEN-EN13606-CLUSTER_. _DrugDrug-Interaction.v1_ augmentation archetype for the drug–drug interactions EHR augmentation. (**b**) The _CEN-EN13606-CLUSTER_. _DisseseTreatment.v1_ augmentation archetype for the disease-related treatments’ EHR augmentation. augmentation archetypes and the augmented archetype must be modeled as part of the process of designing an augmented EHR. The design stage concludes once the required resources have been identified and/or defined: EOI paths, target dataset, terminological mapping service, SPARQL queries, arguments to build EOI binding triples, augmentation archetypes, and augmented archetype, in addition to their corresponding mappings. At runtime, only an instance of the initial EHR archetype is required to execute the workflow and generate an instance of the augmented archetype. Figure 14 shows the augmentation contents for the use case, normalized according to the augmentation archetypes. Figure 15 illustrates the instance of the augmented archetype generated for the use case. \begin{table}
\begin{tabular}{c c c} \hline \hline
**Resource** & **Source Schema(s)** & **Target Schema** \\ \hline Drug-drug interactions augmentation content & XML Schema for SPARQL query results &
\begin{tabular}{} _CEN-EN13606-_ \\ _CLUSTER.DrugDrugInteraction.v1_ \\ _CEN-EN13606-CLUSTER._ \\ _DiseaseTreatment.v1_ \\ _COMPOSITION.HistoriaClinicaResumtida.v1_ \\ _The drug-drug interactions archetype CEN-_EN13606-CLUSTER.DrugDrugInteraction.v1_ \\ _EN13606-CLUSTER.DrugDrugInteraction.v1_ \\ _The disease-related treatments archetype CEN-EN13606-CLUSTER.DiseaseTreatment.v1_ \\ \hline \hline \end{tabular}
\end{table} 
Table 4: List of mapping specifications defined to obtain the augmented summary EHR. The mappings were stated using the LinkEHR platform. For each mapping specification, LinkEHR built a XQuery script whose execution converts data instances of the source schema to data instances of the target schema. Figure 13: Archetypes’ visualization from LinkEHR. **(a)** The initial EHR archetype _CEN-EN13606-COMPOSITION.HistoriaClinicaResumtida.v1_. The EOIs used in this use case are highlighted. **(b)** The augmented archetype _CEN-EN13606-COMPOSITION.HistoriaClinicaResumtidaAugmental.v1_, which is similar to the initial EHR archetype but includes archetype slots for the augmentation archetypes. Figure 14: HTML representation of augmentation contents. (**a**) The augmentation content of the drug-drug interactions’ EHR augmentation, formatted according to the augmentation archetype _CEN-EN13606-CLUSTER_. _DrugDrugInteraction.v1_. (**b**) The augmentation content of the disease-related treatments’ EHR augmentation, formatted according to the augmentation archetype _CEN-EN13606-CLUSTER_. _DiseaseTreatment.v1_. Figure 15: An HTML representation of the augmented summary EHR extract, an instance of the augmented archetype _CEN-EN13606-COMPOSITION.HistoriaClinicaResumidaAugmented.v1_ including the augmented content from (**a**) drug–drug interactions’ and (**b**) disease-related treatments’ EHR augmentations.