# The Need for Machine-Processable Agreements in Health Data Management +
## 2 Real Health Use Cases and Requirements of Data Sharing
\begin{table}
\begin{tabular}{c l l l l} \hline \hline
**id** & **Name** & **Disease Pattern** & **User** & **Sharing Policy** \\ \hline \multirow{3}{*}{UC1} & \multirow{3}{*}{Basic} & \multirow{3}{*}{Autosomal Dominant} & Patient [PERSON] & Share with my siblings and children. \\ \cline{3-4}  & & & [PERSON]’s twin & Never share with brother [PERSON]. \\ \cline{3-4}  & & & Clinician & Share with first degree relatives \\ \hline \multirow{3}{*}{UC2} & \multirow{3}{*}{Family vs. Pedigree} & \multirow{3}{*}{X-linked Receive} & Patient [PERSON] & Share all information with all siblings. \\ \cline{3-4}  & & & Clinician & Share with mother and her children. \\ \hline \multirow{3}{*}{UC3} & \multirow{3}{*}{Age Concerns} & \multirow{3}{*}{Autosomal Dominant} & Patient [PERSON] & Share with my children, siblings. \\ \cline{3-4}  & & & [PERSON]’s partner & Share with the children after they are 15. \\ \cline{3-4}  & & & Clinicalian & Share with first degree relatives \\ \hline \multirow{3}{*}{UC4} & \multirow{3}{*}{Anonymous} & \multirow{3}{*}{X-linked Receive} & Patient [PERSON] & Share with all my children, but anonymize information. \\ \cline{3-4}  & & & Clinician & Share with mother and her children. \\ \hline \multirow{3}{*}{UC5} & \multirow{3}{*}{Conditions} & \multirow{3}{*}{Gonadal Mosaicism} & Patient [PERSON] & Share all information with all my children. Don’t share the results with my nieces and nephews directly, share with their moms. \\ \cline{3-4}  & & & Clinician & Share with children. \\ \hline \multirow{3}{*}{UC6} & \multirow{3}{*}{Order Matters} & \multirow{3}{*}{Autosomal Receive} & Patient [PERSON] & Share with my sister only after my mother has been informed. \\ \cline{3-4}  & & & Clinician & Share with spouse. If carrier, share with all children. \\ \hline \multirow{3}{*}{UC7} & \multirow{3}{*}{Groups of Documents} & \multirow{3}{*}{Somatic mutation} & Patient [PERSON] & My children to see one of, not both the results. \\ \cline{3-4}  & & & Clinician & –(not heritable) \\ \hline \hline \end{tabular}
\end{table} 
Table 1: Genetic sharing use cases with multi-party consent needs. The clinician recommends that [PERSON]'s partner be shared with and tested. If [PERSON]'s partner is a carrier, then all children should be shared with and tested. At the same time, [PERSON] has other time-sensitive sharing concerns. She does not want her sister to know anything until her mother is informed. Finally, UC7 acknowledges that clinical test results can take several forms, from full tests results, through to summaries and anonymized results. In this case, [PERSON] has a somatic mutation that has resulted in a disease. A series of tests have identified that [PERSON] does not have an inheritable genetic disease, and he only wishes to share some pieces of that information. In fact, [PERSON] is willing for _either_ the genetic test showing no chromosomal abnormalities _or_ the screen for specific genetic markers to be shared, but not both. The clinician does not recommend sharing with any additional individuals because the underlying cause was found to be a somatic mutation, not an inherited genetic variant. This analysis exposes several requirements with major ones being:  
1. The need to define complex descriptions of individuals which you cannot always predetermine. A privacy policy management and data sharing system should have abilities to define complex classes such as the complex classes in ontologies or description logics [11]. 2. The need to impose sharing dependencies, such as decisions to share based on history of sharing, or imposing a particular time order to the sharing of data or information. 3. The need to capture, actions, obligations but of equal importance, suggestions or instigations for sharing. The fact that a clinician suggests that the patient should share information with several individuals needs to be recorded as a first-class citizen in the events that are taking place in the data management system. This might be important for historic, legal or accountability reasons. 4.