InDiGenous/InDiGenous.html at main · DocNikDS/InDiGenous · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head>

<meta charset="utf-8">
<meta name="generator" content="quarto-1.8.25">

<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">

<meta name="author" content="Nik Danilov">
<meta name="dcterms.date" content="2025-01-01">

<title>InDiGenous: A National Genomic Identity Infrastructure for Personalized and Population Health</title>
<style>
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
div.columns{display: flex; gap: min(4vw, 1.5em);}
div.column{flex: auto; overflow-x: auto;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list{list-style: none;}
ul.task-list li input[type="checkbox"] {
  width: 0.8em;
  margin: 0 0.8em 0.2em -1em; /* quarto-specific, see https://github.com/quarto-dev/quarto-cli/issues/4556 */
  vertical-align: middle;
}
</style>


<script src="InDiGenous_files/libs/clipboard/clipboard.min.js"></script>
<script src="InDiGenous_files/libs/quarto-html/quarto.js" type="module"></script>
<script src="InDiGenous_files/libs/quarto-html/tabsets/tabsets.js" type="module"></script>
<script src="InDiGenous_files/libs/quarto-html/axe/axe-check.js" type="module"></script>
<script src="InDiGenous_files/libs/quarto-html/popper.min.js"></script>
<script src="InDiGenous_files/libs/quarto-html/tippy.umd.min.js"></script>
<script src="InDiGenous_files/libs/quarto-html/anchor.min.js"></script>
<link href="InDiGenous_files/libs/quarto-html/tippy.css" rel="stylesheet">
<link href="InDiGenous_files/libs/quarto-html/quarto-syntax-highlighting-7b89279ff1a6dce999919e0e67d4d9ec.css" rel="stylesheet" id="quarto-text-highlighting-styles">
<script src="InDiGenous_files/libs/bootstrap/bootstrap.min.js"></script>
<link href="InDiGenous_files/libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
<link href="InDiGenous_files/libs/bootstrap/bootstrap-4d7f0bce1131f3e5f9547cd857cfbfc8.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="light">
<link href="InDiGenous_files/libs/htmltools-fill-0.5.8.1/fill.css" rel="stylesheet">

<script src="InDiGenous_files/libs/htmlwidgets-1.6.4/htmlwidgets.js"></script>

<script src="InDiGenous_files/libs/d3-3.3.8/d3.min.js"></script>

<script src="InDiGenous_files/libs/dagre-0.4.0/dagre-d3.min.js"></script>

<link href="InDiGenous_files/libs/mermaid-0.3.0/dist/mermaid.css" rel="stylesheet">

<script src="InDiGenous_files/libs/mermaid-0.3.0/dist/mermaid.slim.min.js"></script>

<link href="InDiGenous_files/libs/DiagrammeR-styles-0.2/styles.css" rel="stylesheet">

<script src="InDiGenous_files/libs/chromatography-0.1/chromatography.js"></script>

<script src="InDiGenous_files/libs/DiagrammeR-binding-1.0.11/DiagrammeR.js"></script>

<script src="InDiGenous_files/libs/kePrint-0.0.1/kePrint.js"></script>

<link href="InDiGenous_files/libs/lightable-0.0.1/lightable.css" rel="stylesheet">


</head>

<body class="quarto-light">

<div id="quarto-content" class="page-columns page-rows-contents page-layout-article">
<div id="quarto-margin-sidebar" class="sidebar margin-sidebar">
  <nav id="TOC" role="doc-toc" class="toc-active">
    <h2 id="toc-title">Table of contents</h2>

  <ul>
  <li><a href="#i.-background-and-business-requirement" id="toc-i.-background-and-business-requirement" class="nav-link active" data-scroll-target="#i.-background-and-business-requirement">I. Background and business requirement</a>
  <ul class="collapse">
  <li><a href="#background" id="toc-background" class="nav-link" data-scroll-target="#background">Background</a></li>
  <li><a href="#current-challenges" id="toc-current-challenges" class="nav-link" data-scroll-target="#current-challenges">Current challenges</a></li>
  <li><a href="#business-requirement" id="toc-business-requirement" class="nav-link" data-scroll-target="#business-requirement">Business requirement</a></li>
  <li><a href="#indigenous-potential-impact" id="toc-indigenous-potential-impact" class="nav-link" data-scroll-target="#indigenous-potential-impact">InDiGenous’ potential impact</a></li>
  </ul></li>
  <li><a href="#ii.-goals-of-the-proposed-medical-information-system" id="toc-ii.-goals-of-the-proposed-medical-information-system" class="nav-link" data-scroll-target="#ii.-goals-of-the-proposed-medical-information-system">II. Goals of the proposed medical information system</a></li>
  <li><a href="#iii.-current-state-analysis" id="toc-iii.-current-state-analysis" class="nav-link" data-scroll-target="#iii.-current-state-analysis">III. Current state analysis</a>
  <ul class="collapse">
  <li><a href="#existing-gaps-in-gd-utilization" id="toc-existing-gaps-in-gd-utilization" class="nav-link" data-scroll-target="#existing-gaps-in-gd-utilization">Existing gaps in GD utilization</a></li>
  <li><a href="#privacy-concerns-and-ethical-barriers" id="toc-privacy-concerns-and-ethical-barriers" class="nav-link" data-scroll-target="#privacy-concerns-and-ethical-barriers">Privacy concerns and ethical barriers</a></li>
  <li><a href="#underutilization-of-gd-in-ph-research" id="toc-underutilization-of-gd-in-ph-research" class="nav-link" data-scroll-target="#underutilization-of-gd-in-ph-research">Underutilization of GD in PH research</a></li>
  <li><a href="#current-information-systems-and-their-limitations" id="toc-current-information-systems-and-their-limitations" class="nav-link" data-scroll-target="#current-information-systems-and-their-limitations">Current information systems and their limitations</a></li>
  </ul></li>
  <li><a href="#iv.-description-of-the-project" id="toc-iv.-description-of-the-project" class="nav-link" data-scroll-target="#iv.-description-of-the-project">IV. Description of the project</a>
  <ul class="collapse">
  <li><a href="#overview" id="toc-overview" class="nav-link" data-scroll-target="#overview">Overview</a></li>
  <li><a href="#core-functionality" id="toc-core-functionality" class="nav-link" data-scroll-target="#core-functionality">Core functionality</a></li>
  <li><a href="#integration-and-data-flow" id="toc-integration-and-data-flow" class="nav-link" data-scroll-target="#integration-and-data-flow">Integration and data flow</a></li>
  <li><a href="#gui-and-access-control" id="toc-gui-and-access-control" class="nav-link" data-scroll-target="#gui-and-access-control">GUI and access control</a></li>
  <li><a href="#comparison-with-existing-systems" id="toc-comparison-with-existing-systems" class="nav-link" data-scroll-target="#comparison-with-existing-systems">Comparison with existing systems</a></li>
  </ul></li>
  <li><a href="#v.-stakeholders-and-users" id="toc-v.-stakeholders-and-users" class="nav-link" data-scroll-target="#v.-stakeholders-and-users">V. Stakeholders and users</a>
  <ul class="collapse">
  <li><a href="#patients" id="toc-patients" class="nav-link" data-scroll-target="#patients">1. Patients</a></li>
  <li><a href="#healthcare-providers" id="toc-healthcare-providers" class="nav-link" data-scroll-target="#healthcare-providers">2. Healthcare providers</a></li>
  <li><a href="#ph-researchers" id="toc-ph-researchers" class="nav-link" data-scroll-target="#ph-researchers">3. PH researchers</a></li>
  <li><a href="#it-developers-and-system-administrators" id="toc-it-developers-and-system-administrators" class="nav-link" data-scroll-target="#it-developers-and-system-administrators">4. IT developers and system administrators</a></li>
  <li><a href="#state-regulatory-bodies" id="toc-state-regulatory-bodies" class="nav-link" data-scroll-target="#state-regulatory-bodies">5. State regulatory bodies</a></li>
  <li><a href="#research-institutions-and-universities" id="toc-research-institutions-and-universities" class="nav-link" data-scroll-target="#research-institutions-and-universities">6. Research institutions and universities</a></li>
  <li><a href="#forensic-and-security-agencies" id="toc-forensic-and-security-agencies" class="nav-link" data-scroll-target="#forensic-and-security-agencies">7. Forensic and security agencies</a></li>
  </ul></li>
  <li><a href="#vi.-success-metrics" id="toc-vi.-success-metrics" class="nav-link" data-scroll-target="#vi.-success-metrics">VI. Success metrics</a>
  <ul class="collapse">
  <li><a href="#user-adoption-and-engagement" id="toc-user-adoption-and-engagement" class="nav-link" data-scroll-target="#user-adoption-and-engagement">1. User adoption and engagement</a></li>
  <li><a href="#data-security-and-privacy-compliance" id="toc-data-security-and-privacy-compliance" class="nav-link" data-scroll-target="#data-security-and-privacy-compliance">2. Data security and privacy compliance</a></li>
  <li><a href="#research-impact-and-utilization" id="toc-research-impact-and-utilization" class="nav-link" data-scroll-target="#research-impact-and-utilization">3. Research impact and utilization</a></li>
  <li><a href="#patient-outcomes-and-clinical-improvements" id="toc-patient-outcomes-and-clinical-improvements" class="nav-link" data-scroll-target="#patient-outcomes-and-clinical-improvements">4. Patient outcomes and clinical improvements</a></li>
  <li><a href="#reproductive-and-family-planning-use" id="toc-reproductive-and-family-planning-use" class="nav-link" data-scroll-target="#reproductive-and-family-planning-use">5. Reproductive and family planning use</a></li>
  <li><a href="#ph-contributions" id="toc-ph-contributions" class="nav-link" data-scroll-target="#ph-contributions">6. PH contributions</a></li>
  </ul></li>
  <li><a href="#vii.-legal-and-ethical-framework" id="toc-vii.-legal-and-ethical-framework" class="nav-link" data-scroll-target="#vii.-legal-and-ethical-framework">VII. Legal and ethical framework</a>
  <ul class="collapse">
  <li><a href="#applicable-legal-frameworks" id="toc-applicable-legal-frameworks" class="nav-link" data-scroll-target="#applicable-legal-frameworks">Applicable legal frameworks</a></li>
  <li><a href="#consent-architecture" id="toc-consent-architecture" class="nav-link" data-scroll-target="#consent-architecture">Consent architecture</a></li>
  <li><a href="#surveillance-risk-mitigation" id="toc-surveillance-risk-mitigation" class="nav-link" data-scroll-target="#surveillance-risk-mitigation">Surveillance risk mitigation</a></li>
  <li><a href="#the-legislative-gap" id="toc-the-legislative-gap" class="nav-link" data-scroll-target="#the-legislative-gap">The legislative gap</a></li>
  </ul></li>
  <li><a href="#viii.-implementation-roadmap" id="toc-viii.-implementation-roadmap" class="nav-link" data-scroll-target="#viii.-implementation-roadmap">VIII. Implementation roadmap</a></li>
  <li><a href="#references" id="toc-references" class="nav-link" data-scroll-target="#references">References</a>
  <ul class="collapse">
  <li><a href="#legal-and-regulatory-frameworks" id="toc-legal-and-regulatory-frameworks" class="nav-link" data-scroll-target="#legal-and-regulatory-frameworks">Legal and regulatory frameworks</a></li>
  <li><a href="#technical-standards" id="toc-technical-standards" class="nav-link" data-scroll-target="#technical-standards">Technical standards</a></li>
  </ul></li>
  <li><a href="#appendices" id="toc-appendices" class="nav-link" data-scroll-target="#appendices">Appendices</a>
  <ul class="collapse">
  <li><a href="#appendix-a-patient-access-control-guide" id="toc-appendix-a-patient-access-control-guide" class="nav-link" data-scroll-target="#appendix-a-patient-access-control-guide">Appendix A: Patient access control guide</a></li>
  <li><a href="#appendix-b-applicable-data-protection-standards-comparative-summary-tbl-standards" id="toc-appendix-b-applicable-data-protection-standards-comparative-summary-tbl-standards" class="nav-link" data-scroll-target="#appendix-b-applicable-data-protection-standards-comparative-summary-tbl-standards">Appendix B: Applicable data protection standards: Comparative summary (<em>Table&nbsp;5</em>)</a></li>
  </ul></li>
  </ul>
</nav>
</div>
<main class="content" id="quarto-document-content">

<header id="title-block-header" class="quarto-title-block default">
<div class="quarto-title">
<h1 class="title">InDiGenous: A National Genomic Identity Infrastructure for Personalized and Population Health</h1>
<p class="subtitle lead">A Medical Informatics System Design Proposal</p>
</div>


<div class="quarto-title-meta-author">
  <div class="quarto-title-meta-heading">Author</div>
  <div class="quarto-title-meta-heading">Affiliation</div>

    <div class="quarto-title-meta-contents">
    <p class="author">Nik Danilov <a href="mailto:danilov.md@gmail.com" class="quarto-title-author-email"><i class="bi bi-envelope"></i></a> </p>
  </div>
  <div class="quarto-title-meta-contents">
        <p class="affiliation">
            School of Public Health, University of Haifa | Lady Davis Carmel Medical Center, Haifa, Israel
          </p>
      </div>
  </div>

<div class="quarto-title-meta">


    <div>
    <div class="quarto-title-meta-heading">Published</div>
    <div class="quarto-title-meta-contents">
      <p class="date">2025</p>
    </div>
  </div>


  </div>


</header>


<div class="callout callout-style-simple callout-note no-icon">
<div class="callout-body d-flex">
<div class="callout-icon-container">
<i class="callout-icon no-icon"></i>
</div>
<div class="callout-body-container">
<p><em>Course instructor: Yaron Denekamp, MD, MSc | Medical Informatics, School of Public Health, University of Haifa</em></p>
</div>
</div>
</div>
<hr>
<div class="callout callout-style-simple callout-note">
<div class="callout-body d-flex">
<div class="callout-icon-container">
<i class="callout-icon"></i>
</div>
<div class="callout-body-container">
<p><em>It is a system design proposal developed as a final project for the Medical Informatics course (School of Public Health, University of Haifa, 2025). It describes a conceptual architecture for a national genomic ID system — designed as an exercise in applied health informatics system thinking, not as a description of an implemented or funded system.</em></p>
</div>
</div>
</div>
<section id="i.-background-and-business-requirement" class="level2">
<h2 class="anchored" data-anchor-id="i.-background-and-business-requirement">I. Background and business requirement</h2>
<section id="background" class="level3">
<h3 class="anchored" data-anchor-id="background">Background</h3>
<p>The integration of individual genomic data (GD) into routine clinical practice has the potential to significantly enhance personalized healthcare — allowing physicians to tailor diagnostics and treatment to each patient’s genetic profile. In current medical systems, however, GD is typically kept separate from general electronic health records (EHRs), limiting its practical utility at the point of care. This separation hinders personalized medicine, slows genomic research, and restricts the application of GD in public health (PH).</p>
<p>Beyond disease risk prediction, GD determines the effectiveness and safety of many treatments — from oncological targeted therapy to pharmacogenomic drug dosing. Its integration with other medical data could substantially improve outcomes in conditions where genetics plays a central role: hereditary cancers, cardiovascular diseases, metabolic and neurological disorders, and others.</p>
</section>
<section id="current-challenges" class="level3">
<h3 class="anchored" data-anchor-id="current-challenges">Current challenges</h3>
<p>Three core barriers obstruct effective GD utilization in healthcare:</p>
<ul>
<li><p>Data fragmentation: Genomic information is stored in specialized laboratory databases (DBs) disconnected from EHRs, preventing clinicians from accessing it during routine consultations.</p></li>
<li><p>Privacy concerns: GD is uniquely sensitive — it carries implications not only for an individual but for her/his biological relatives across generations. The risks of unauthorized access, misuse, or discriminatory application create justified reluctance among patients and providers to share it without robust legal and technical safeguards.</p></li>
<li><p>Underutilization in PH: Population-wide GD, essential for genetic epidemiology and the design of targeted preventive interventions, remains largely inaccessible to PH researchers due to the absence of aggregation and anonymization infrastructure.</p></li>
</ul>
</section>
<section id="business-requirement" class="level3">
<h3 class="anchored" data-anchor-id="business-requirement">Business requirement</h3>
<p><strong><em>InDiGenous</em></strong> (<strong>Indi</strong>vidual <strong>Digi</strong>tal <strong>Geno</strong>mic <strong>S</strong>ystem) is a proposed secure digital repository for individual genomic profiles (personalized genomic IDs), accessible by the patient, healthcare providers, and other authorized parties under strictly governed consent conditions.</p>
<p>Its <strong>core objectives</strong> are:</p>
<ul>
<li><p>Patient autonomy: Full patient control over GD — who accesses it, for what purpose, and under what conditions.</p></li>
<li><p>Personalized healthcare: Clinician access to GD within existing EHR workflows, enabling precision diagnostics and treatment.</p></li>
<li><p>PH research: Aggregated, anonymized GD for population-level genetic epidemiology and health policy.</p></li>
</ul>
</section>
<section id="indigenous-potential-impact" class="level3">
<h3 class="anchored" data-anchor-id="indigenous-potential-impact">InDiGenous’ potential impact</h3>
<p><strong><em>InDiGenous</em></strong> bridges the clinical and PH spheres of genomic medicine. Its anticipated impact spans three levels:</p>
<ul>
<li><p>Clinical: More precise treatment, reduced adverse drug reactions, improved outcomes in genetically driven conditions.</p></li>
<li><p>Population: Insights into genetic risk patterns across communities, informing targeted preventive strategies.</p></li>
<li><p>Trust and security: A consent-driven, legally compliant framework that encourages patients to share GD without fear of misuse.</p></li>
</ul>
</section>
</section>
<section id="ii.-goals-of-the-proposed-medical-information-system" class="level2">
<h2 class="anchored" data-anchor-id="ii.-goals-of-the-proposed-medical-information-system">II. Goals of the proposed medical information system</h2>
<p><em>InDiGenous</em> addresses critical gaps in healthcare by providing a centralized, secure platform for individual GD management. Its <strong>primary goals</strong> are as follows:</p>
<ol type="1">
<li><p>Empowerment of patient autonomy: To enable individuals to fully control their GD, including granting and managing access based on informed consent. Patients set access permissions for healthcare providers, researchers, and family members — with granular control over who may view, modify, or utilize specific data elements. This patient-centric architecture is the foundation of the system’s trustworthiness and the prerequisite for broad adoption.</p></li>
<li><p>Facilitation of personalized healthcare: To integrate GD into clinical practice, giving providers access to patient-specific genomic profiles at the point of care. GD enable more precise treatment recommendations — reducing adverse drug reactions, guiding targeted therapy selection, and informing dosing for patients whose genetic profiles affect drug metabolism. For conditions with strong genetic determinants (oncological, cardiovascular, neurological), this integration supports a shift from reactive to proactive, individualized care.</p></li>
<li><p>Support of PH and population-level research: To provide anonymized, aggregated GD supporting research in genomics, genetic epidemiology, and population genetics. Population-level GD allows identification of genetic risk factors prevalent in specific communities, enabling targeted preventive interventions. In the Israeli context — with its distinct population groups (Ashkenazi Jewish, Druze, Bedouin, and others) and elevated carrier frequencies of specific recessive disorders — this capability is of particular epidemiological relevance. The system supports studies linking genetic variants to disease outcomes at the population level, with direct implications for pharmacogenomics, preventive medicine, and health policy.</p></li>
<li><p>Data security and trust: To create a secure digital environment assuring GD privacy and integrity. <em>InDiGenous</em> implements encryption, multi-factor authentication, and detailed access logging for all GD interactions. Compliance with international data protection frameworks — including the European General Data Protection Regulation (GDPR) and the American Health Insurance Portability and Accountability Act (HIPAA) — as well as Israeli national privacy legislation, is built into the system architecture rather than treated as an afterthought.</p></li>
<li><p>Fostering collaboration between clinical and research communities: To facilitate structured, governed data sharing between healthcare providers, researchers, and institutional users. <em>InDiGenous</em> is designed to integrate with EHRs, national ID infrastructure, and research DBs — enabling clinicians and researchers to work from a unified, authoritative GD source. Anonymized datasets are available for clinical trials, epidemiological studies, and PH investigations under defined access conditions.</p></li>
</ol>
</section>
<section id="iii.-current-state-analysis" class="level2">
<h2 class="anchored" data-anchor-id="iii.-current-state-analysis">III. Current state analysis</h2>
<section id="existing-gaps-in-gd-utilization" class="level3">
<h3 class="anchored" data-anchor-id="existing-gaps-in-gd-utilization">Existing gaps in GD utilization</h3>
<p>Despite the established clinical value of GD, its integration within EHR systems remains limited. GD are typically stored in isolated laboratory DBs lacking interoperability with other medical information systems. This fragmentation prevents clinicians from accessing GD in real time during consultations — precisely when it is most needed.</p>
<p>The absence of standardized data-sharing protocols compounds the problem. Without uniform exchange standards — such as HL7 FHIR (Fast Healthcare Interoperability Resources) or GA4GH (Global Alliance for Genomics and Health) frameworks — institutions cannot reliably communicate genomic findings across systems, leading to redundant testing, delays, and inconsistent care.</p>
</section>
<section id="privacy-concerns-and-ethical-barriers" class="level3">
<h3 class="anchored" data-anchor-id="privacy-concerns-and-ethical-barriers">Privacy concerns and ethical barriers</h3>
<p>GD is inherently different from other medical data. It is heritable (implicating biological relatives who have not consented to its collection) and permanent (unlike a password or an account number, a genome cannot be changed if compromised). These properties place GD in a distinct risk category that existing general-purpose privacy frameworks were not designed to address.</p>
<p>Current GD repositories rarely meet the standards required for this sensitivity: encryption at rest and in transit, consent-driven access controls, audit trails, and regulatory compliance. The result is justified patient reluctance to share GD, which in turn constrains both clinical use and research availability.</p>
</section>
<section id="underutilization-of-gd-in-ph-research" class="level3">
<h3 class="anchored" data-anchor-id="underutilization-of-gd-in-ph-research">Underutilization of GD in PH research</h3>
<p>Population-level GD is essential for identifying community-specific genetic risk factors, designing targeted screening programs, and advancing genetic epidemiology. Yet PH research systems generally lack access to it. The barrier is structural: no mechanism exists to aggregate and anonymize GD at scale while preserving individual privacy and maintaining research utility.</p>
<p>This gap is particularly consequential in Israel, where distinct population groups carry elevated frequencies of specific genetic variants — information that is epidemiologically actionable but currently inaccessible in aggregated form.</p>
</section>
<section id="current-information-systems-and-their-limitations" class="level3">
<h3 class="anchored" data-anchor-id="current-information-systems-and-their-limitations">Current information systems and their limitations</h3>
<p>Existing partial solutions each address one dimension of the problem while leaving the others unresolved:</p>
<ul>
<li><p>Standalone genomic DBs (e.g., ClinVar, gnomAD): Specialized repositories for variant data, but without linkage to individual EHRs or clinical outcomes. Useful for research reference but not for point-of-care decision support.</p></li>
<li><p>EHR systems with limited GD modules: Some modern EHRs incorporate basic pharmacogenomic alerts or discrete variant fields, but comprehensive genomic integration — covering the full range of genomic results — remains rare. Consent and access management for GD are typically absent.</p></li>
<li><p>National biometric registries: Israeli biometric DB (operational since 2013) demonstrates that national-scale sensitive biometric data collection is technically and legally feasible. However, it is not linked to health data and has no genomic component.</p></li>
<li><p>PH surveillance systems: Focused on epidemiological and demographic data; GD is not included. The Israel Precision Medicine Partnership (IPMP), launched in 2019 with a mandate to sequence 100,000 Israeli genomes, represents the most direct precursor to <em>InDiGenous</em> — but it remains a research initiative without a clinical integration or patient-access layer.</p></li>
</ul>
<p>The gap <em>InDiGenous</em> addresses is therefore not the absence of GD generation — that capacity exists — but the absence of a governed, integrated, patient-controlled infrastructure for its storage, access, and use across clinical, research, and extended application domains.</p>
</section>
</section>
<section id="iv.-description-of-the-project" class="level2">
<h2 class="anchored" data-anchor-id="iv.-description-of-the-project">IV. Description of the project</h2>
<section id="overview" class="level3">
<h3 class="anchored" data-anchor-id="overview">Overview</h3>
<p><strong><em>InDiGenous</em></strong> is a centralized, secure digital repository for individual genomic profiles — a personalized genomic ID system anchored to the national health/security infrastructure. Its architecture is built around three principles:</p>
<ol type="1">
<li><p>patient sovereignty over GD</p></li>
<li><p>governed interoperability with existing clinical and research systems</p></li>
<li><p>extensibility to non-clinical application domains</p></li>
</ol>
<p>The system is not a genomic sequencing platform. It does not generate GD — it receives, stores, governs access to, and distributes GD produced by accredited clinical and research laboratories. Its role is infrastructural: to be the authoritative, persistent, patient-linked repository that GD currently lack.</p>
</section>
<section id="core-functionality" class="level3">
<h3 class="anchored" data-anchor-id="core-functionality">Core functionality</h3>
<ol type="1">
<li>Centralized storage and secure access:</li>
</ol>
<ul>
<li><p><em>InDiGenous</em> consolidates genomic profiles alongside relevant clinical metadata in a structured, queryable DB. Supported data types include raw sequence data, interpreted variant reports, pharmacogenomic profiles, carrier status, hereditary disease risk assessments, and longitudinal updates as new variants are characterized.</p></li>
<li><p>Access is patient-controlled. Through the <em>InDiGenous</em> graphic user interface (GUI) an individual (“patient”) grants or restricts access to specific data elements for specific recipients — clinicians, researchers, family members, or institutional users — with permissions revocable at any time. Every access event is logged in a tamper-evident audit trail visible to the patient.</p></li>
<li><p>Security architecture includes AES-256 encryption at rest and in transit, multi-factor authentication for all user tiers, role-based access control (RBAC), and periodic third-party security audits.</p></li>
</ul>
<ol start="2" type="1">
<li>Cross-platform availability:</li>
</ol>
<ul>
<li><em>InDiGenous</em> is accessible via web, mobile, and desktop GUIs — designed for both technically proficient users and those with limited digital literacy. The patient-facing interface prioritizes clarity: consent decisions are presented in plain language, access logs are human-readable, and genomic findings are accompanied by lay summaries where clinically appropriate.</li>
</ul>
</section>
<section id="integration-and-data-flow" class="level3">
<h3 class="anchored" data-anchor-id="integration-and-data-flow">Integration and data flow</h3>
<p>The <em><a href="#fig-info-flow" class="quarto-xref">Figure&nbsp;1</a></em> illustrates the core information flow within <em>InDiGenous</em>: how GD enter the system, how they are stored and governed, and how they reach authorized end users across clinical, research, and extended application domains.</p>
<div class="cell">
<div id="fig-info-flow" class="cell-output-display quarto-float quarto-figure quarto-figure-center anchored">
<figure class="quarto-float quarto-float-fig figure">
<div aria-describedby="fig-info-flow-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
<div class="DiagrammeR html-widget html-fill-item" id="htmlwidget-e02a2fa84cce97d3494c" style="width:100%;height:464px;"></div>
<script type="application/json" data-for="htmlwidget-e02a2fa84cce97d3494c">{"x":{"diagram":"\ngraph TD\n    A((Patient / Genome Source)) -->|Raw GD upload| B[InDiGenous Core Repository]\n    B --> C{Consent Engine}\n    C -->|Authorized| D[Clinical EHR Interface]\n    C -->|Authorized| E[Research and PH Module]\n    C -->|Authorized| F[Extended Use Module]\n    C -->|Denied / Revoked| G((Access Blocked))\n    D --> D1[Treating Physician]\n    D --> D2[Pharmacogenomics Alert System]\n    E --> E1[Anonymized Aggregate DB]\n    E1 --> E2[PH Researchers]\n    E1 --> E3[Genetic Epidemiology Studies]\n    F --> F1[Forensic Identification]\n    F --> F2[Reproductive Compatibility Screening]\n    F --> F3[National Security / Personnel ID]\n    B --> H[Audit Log]\n    H -->|Transparent to patient| A\n\n    style A fill:#2166ac,color:#ffffff,stroke:#2166ac\n    style G fill:#d73027,color:#ffffff,stroke:#d73027\n    style C fill:#f4a736,color:#000000,stroke:#e08010\n    style B fill:#1a9850,color:#ffffff,stroke:#1a9850\n    style H fill:#c2a5cf,color:#000000,stroke:#762a83\n    style D fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style E fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style F fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style D1 fill:#f7f7f7,color:#000000,stroke:#999999\n    style D2 fill:#f7f7f7,color:#000000,stroke:#999999\n    style E1 fill:#f7f7f7,color:#000000,stroke:#999999\n    style E2 fill:#f7f7f7,color:#000000,stroke:#999999\n    style E3 fill:#f7f7f7,color:#000000,stroke:#999999\n    style F1 fill:#f7f7f7,color:#000000,stroke:#999999\n    style F2 fill:#f7f7f7,color:#000000,stroke:#999999\n    style F3 fill:#f7f7f7,color:#000000,stroke:#999999\n"},"evals":[],"jsHooks":[]}</script>
</div>
<figcaption class="quarto-float-caption-bottom quarto-float-caption quarto-float-fig" id="fig-info-flow-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
Figure&nbsp;1: Core information flow within InDiGenous
</figcaption>
</figure>
</div>
</div>
<ol type="1">
<li>EHR integration:</li>
</ol>
<p><em>InDiGenous</em> communicates with existing EHR systems via HL7 FHIR APIs, enabling clinicians to retrieve relevant GD directly within their clinical workflow — without logging into a separate system. A pharmacogenomic alert layer flags drug-gene interactions at the point of prescribing, consistent with CPIC (Clinical Pharmacogenomics Implementation Consortium) guidelines.</p>
<ol start="2" type="1">
<li>National health system linkage:</li>
</ol>
<p>Patient identity within <em>InDiGenous</em> is anchored to the Israeli national ID number, enabling linkage with HMO records (Clalit, Maccabi, Meuhedet, Leumit), the Ministry of Interior, and — under defined legal conditions — national security infrastructure. This linkage eliminates the identity verification burden that currently impedes cross-institutional data sharing.</p>
<ol start="3" type="1">
<li>PH research integration:</li>
</ol>
<p>A dedicated research module provides PH researchers with access to anonymized aggregated GD under a data access agreement framework modeled on GA4GH standards. Individual-level data is never exposed; researchers interact with de-identified datasets or summary statistics generated server-side.</p>
</section>
<section id="gui-and-access-control" class="level3">
<h3 class="anchored" data-anchor-id="gui-and-access-control">GUI and access control</h3>
<p>The <em><a href="#fig-access-tiers" class="quarto-xref">Figure&nbsp;2</a></em> shows the tiered access architecture of <em>InDiGenous</em>, from the patient at the center to institutional users at the periphery.</p>
<div class="cell">
<div id="fig-access-tiers" class="cell-output-display quarto-float quarto-figure quarto-figure-center anchored">
<figure class="quarto-float quarto-float-fig figure">
<div aria-describedby="fig-access-tiers-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
<div class="DiagrammeR html-widget html-fill-item" id="htmlwidget-c2044a9c52cc6b19fcbe" style="width:100%;height:464px;"></div>
<script type="application/json" data-for="htmlwidget-c2044a9c52cc6b19fcbe">{"x":{"diagram":"\ngraph LR\n    P((Patient GD Owner)) -->|Full control| CE{Consent Engine}\n    CE -->|Tier 1| T1[Treating Clinicians]\n    CE -->|Tier 2| T2[Researchers]\n    CE -->|Tier 3| T3[Family Members]\n    CE -->|Tier 4| T4[Forensic and Security]\n    CE -->|Tier 5| T5[IT Administrators]\n    CE -->|Denied| G((Access Blocked))\n\n    style P fill:#2166ac,color:#ffffff,stroke:#2166ac\n    style G fill:#d73027,color:#ffffff,stroke:#d73027\n    style CE fill:#f4a736,color:#000000,stroke:#e08010\n    style T1 fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style T2 fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style T3 fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style T4 fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style T5 fill:#f7f7f7,color:#000000,stroke:#999999\n"},"evals":[],"jsHooks":[]}</script>
</div>
<figcaption class="quarto-float-caption-bottom quarto-float-caption quarto-float-fig" id="fig-access-tiers-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
Figure&nbsp;2: Tiered access architecture of InDiGenous
</figcaption>
</figure>
</div>
</div>
<ol type="1">
<li>Patient-centric design:</li>
</ol>
<p>The patient GUI presents GD access decisions in plain language. Consent is granular: e.g., a patient may authorize her/his treating oncologist to view tumor-relevant somatic variants while withholding pharmacogenomic data from the same clinician, or grant a researcher access to anonymized carrier status while blocking all clinical access. Notifications are issued for every access event.</p>
<ol start="2" type="1">
<li>Clinical provider GUI:</li>
</ol>
<p>Clinicians access a condition-relevant GD dashboard integrated within the EHR. Pharmacogenomic flags, hereditary risk alerts, and variant summaries are displayed contextually — presented at the moment of clinical relevance rather than requiring active retrieval.</p>
<ol start="3" type="1">
<li>Research and institutional access:</li>
</ol>
<p>Researchers receive access to anonymized datasets exportable in standard formats (VCF, FHIR Genomics, CSV). Institutional users in forensic or security domains access the system under a separate legal authorization pathway, with independent audit logging and mandatory judicial or ministerial oversight.</p>
</section>
<section id="comparison-with-existing-systems" class="level3">
<h3 class="anchored" data-anchor-id="comparison-with-existing-systems">Comparison with existing systems</h3>
<table class="caption-top table">
<colgroup>
<col style="width: 25%">
<col style="width: 25%">
<col style="width: 25%">
<col style="width: 25%">
</colgroup>
<thead>
<tr class="header">
<th>Feature</th>
<th>Standalone genomic DBs</th>
<th>EHR genomic modules</th>
<th>InDiGenous</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>Patient access and control</td>
<td>None</td>
<td>Limited</td>
<td>Full</td>
</tr>
<tr class="even">
<td>EHR integration</td>
<td>None</td>
<td>Partial</td>
<td>Complete (FHIR)</td>
</tr>
<tr class="odd">
<td>Cross-institutional portability</td>
<td>None</td>
<td>Rare</td>
<td>By design</td>
</tr>
<tr class="even">
<td>PH research access</td>
<td>Reference only</td>
<td>None</td>
<td>Governed aggregate</td>
</tr>
<tr class="odd">
<td>Extended use domains</td>
<td>None</td>
<td>None</td>
<td>Forensic, security, reproductive</td>
</tr>
<tr class="even">
<td>National ID linkage</td>
<td>None</td>
<td>None</td>
<td>Core feature</td>
</tr>
<tr class="odd">
<td>Consent architecture</td>
<td>None</td>
<td>Basic</td>
<td>Granular, audited</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="v.-stakeholders-and-users" class="level2">
<h2 class="anchored" data-anchor-id="v.-stakeholders-and-users">V. Stakeholders and users</h2>
<p>The success of <em>InDiGenous</em> depends on engaging a clearly defined set of stakeholders, each with distinct roles, access levels, and interests. The <em><a href="#tbl-stakeholders" class="quarto-xref">Table&nbsp;1</a></em> summarizes the stakeholder ecosystem before each group is described in detail.</p>
<div class="cell">
<div id="tbl-stakeholders" class="cell quarto-float quarto-figure quarto-figure-center anchored">
<figure class="quarto-float quarto-float-tbl figure">
<figcaption class="quarto-float-caption-top quarto-float-caption quarto-float-tbl" id="tbl-stakeholders-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
Table&nbsp;1: InDiGenous stakeholder groups: primary roles and benefits
</figcaption>
<div aria-describedby="tbl-stakeholders-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
<div class="cell-output-display">
<table class="table table-striped table-hover do-not-create-environment cell caption-top table-sm small">
<thead>
<tr class="header">
<th style="text-align: left;" data-quarto-table-cell-role="th">Stakeholder group</th>
<th style="text-align: left;" data-quarto-table-cell-role="th">Primary role</th>
<th style="text-align: left;" data-quarto-table-cell-role="th">Primary benefit</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: left; width: 12em; font-weight: bold;">Patients</td>
<td style="text-align: left;">GD owners and consent controllers</td>
<td style="text-align: left;">Autonomy, personalized care, reproductive counseling</td>
</tr>
<tr class="even">
<td style="text-align: left; width: 12em; font-weight: bold;">Healthcare providers</td>
<td style="text-align: left;">Clinical GD consumers at point of care</td>
<td style="text-align: left;">Precision treatment, pharmacogenomic safety, continuity of care</td>
</tr>
<tr class="odd">
<td style="text-align: left; width: 12em; font-weight: bold;">PH researchers</td>
<td style="text-align: left;">Anonymized aggregate GD consumers</td>
<td style="text-align: left;">Population genetic epidemiology, PH policy development</td>
</tr>
<tr class="even">
<td style="text-align: left; width: 12em; font-weight: bold;">IT developers / system administrators</td>
<td style="text-align: left;">System builders, maintainers, security enforcers</td>
<td style="text-align: left;">Technically robust, compliant, trusted platform</td>
</tr>
<tr class="odd">
<td style="text-align: left; width: 12em; font-weight: bold;">State regulatory bodies</td>
<td style="text-align: left;">Legal oversight, compliance monitoring</td>
<td style="text-align: left;">Governed national GD infrastructure</td>
</tr>
<tr class="even">
<td style="text-align: left; width: 12em; font-weight: bold;">Research institutions and universities</td>
<td style="text-align: left;">Research access, academic training</td>
<td style="text-align: left;">High-quality anonymized GD for studies and teaching</td>
</tr>
<tr class="odd">
<td style="text-align: left; width: 12em; font-weight: bold;">Forensic and security agencies</td>
<td style="text-align: left;">Legally authorized extended-use access</td>
<td style="text-align: left;">Forensic identification, personnel ID, mass casualty response</td>
</tr>
</tbody>
</table>
</div>
</div>
</figure>
</div>
</div>
<section id="patients" class="level3">
<h3 class="anchored" data-anchor-id="patients">1. Patients</h3>
<p><strong><em>Patients</em></strong> will be the central stakeholders — they will own their GD and control all access to them. This is not merely a design preference but a legal and ethical requirement, for <strong><em>GD</em></strong> are personal property with multigenerational implications.</p>
<ul>
<li><p>GD control and privacy: Patients will grant, restrict, and revoke access at any time, with full visibility of who has accessed their GD and when.</p></li>
<li><p>Personalized healthcare: GD integrated into the EHR will enable clinicians to deliver precision diagnostics and treatment without the patient needing to manage GD transfer between institutions.</p></li>
<li><p>Reproductive and family counseling: For patients with hereditary conditions or carrier status, <em>InDiGenous</em> will provide a structured basis for informed reproductive decision-making within existing genetic counseling frameworks.</p></li>
</ul>
</section>
<section id="healthcare-providers" class="level3">
<h3 class="anchored" data-anchor-id="healthcare-providers">2. Healthcare providers</h3>
<p>Clinicians will access patient GD within their existing EHR workflow — no separate login, no manual retrieval. The system will surface relevant genomic findings contextually: pharmacogenomic alerts at the point of prescribing, hereditary risk flags during preventive consultations, tumor variant summaries in oncology.</p>
<ul>
<li><p>Precision treatment: Drug selection and dosing informed by pharmacogenomic profile, reducing adverse reactions.</p></li>
<li><p>Continuity of care: GD will be accessible across institutions, eliminating redundant testing when patients transfer.</p></li>
<li><p>Clinical decision support: Variant interpretation linked to current guidelines (CPIC, ACMG).</p></li>
</ul>
</section>
<section id="ph-researchers" class="level3">
<h3 class="anchored" data-anchor-id="ph-researchers">3. PH researchers</h3>
<p>PH researchers will access anonymized, aggregated GD under a governed data access framework. Individual-level data will be never exposed. Researchers will interact with de-identified datasets or server-side summary statistics.</p>
<ul>
<li><p>Genetic epidemiology: Population-level GD will enable identification of community-specific risk factors — of particular relevance in Israeli population subgroups.</p></li>
<li><p>Policy development: Evidence base for targeted screening programs and preventive interventions.</p></li>
<li><p>Ethical compliance: GA4GH-aligned data access agreements will ensure that research use remains within consented boundaries.</p></li>
</ul>
</section>
<section id="it-developers-and-system-administrators" class="level3">
<h3 class="anchored" data-anchor-id="it-developers-and-system-administrators">4. IT developers and system administrators</h3>
<p>This group will build and maintain the platform — ensuring security, reliability, and regulatory compliance. They will have system-level access only; no GD content wiil be accessible to them.</p>
<ul>
<li><p>Security architecture: Encryption, access logging, penetration testing, incident response.</p></li>
<li><p>System reliability: Uptime, performance, cross-platform consistency.</p></li>
<li><p>Compliance: Ongoing alignment with GDPR, HIPAA, Israeli Privacy Protection Law, and evolving GD governance standards.</p></li>
</ul>
</section>
<section id="state-regulatory-bodies" class="level3">
<h3 class="anchored" data-anchor-id="state-regulatory-bodies">5. State regulatory bodies</h3>
<p>The Ministry of Health, the Privacy Protection Authority, and relevant oversight bodies will define the legal framework within which <em>InDiGenous</em> operates — approving data access policies, auditing compliance, and updating governance as the regulatory landscape evolves.</p>
<ul>
<li><p>Data protection: Ensuring national and international privacy standards are met.</p></li>
<li><p>PH planning: Leveraging aggregated GD insights for national health strategy.</p></li>
<li><p>Quality control: Independent audit of data management practices.</p></li>
</ul>
</section>
<section id="research-institutions-and-universities" class="level3">
<h3 class="anchored" data-anchor-id="research-institutions-and-universities">6. Research institutions and universities</h3>
<p>Academic institutions will access anonymized GD for studies in genomics, genetic epidemiology, personalized medicine, etc. <em>InDiGenous</em> will also serve as a teaching resource — exposing students to real-world GD infrastructure within an ethical, governed framework.</p>
</section>
<section id="forensic-and-security-agencies" class="level3">
<h3 class="anchored" data-anchor-id="forensic-and-security-agencies">7. Forensic and security agencies</h3>
<p>This stakeholder group is absent from conventional genomic ID proposals but is directly relevant in the Israeli context. The National Forensic Institute (Abu Kabir), Israeli Police, IDF Medical Corps, and relevant security services will be able to access <em>InDiGenous</em> under a separate legal authorization pathway — distinct from the clinical and research tiers — with mandatory judicial or ministerial oversight and independent audit logging.</p>
<ul>
<li><p>Forensic identification: Identification in mass casualty events and criminal investigations.</p></li>
<li><p>Personnel ID: Identity verification for military and security personnel in field conditions.</p></li>
</ul>
<p>Access in this tier will never be self-authorized by the patient consent engine alone — it will require external legal authorization, logged separately, and subject to independent oversight.</p>
</section>
</section>
<section id="vi.-success-metrics" class="level2">
<h2 class="anchored" data-anchor-id="vi.-success-metrics">VI. Success metrics</h2>
<p>The effectiveness of <em>InDiGenous</em> will be evaluated across six domains. For each, the metric, its rationale, and its measurement method are defined (<em><a href="#tbl-metrics" class="quarto-xref">Table&nbsp;2</a></em>).</p>
<div class="cell">
<div id="tbl-metrics" class="cell quarto-float quarto-figure quarto-figure-center anchored">
<figure class="quarto-float quarto-float-tbl figure">
<figcaption class="quarto-float-caption-top quarto-float-caption quarto-float-tbl" id="tbl-metrics-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
Table&nbsp;2: InDiGenous success metrics by domain
</figcaption>
<div aria-describedby="tbl-metrics-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
<div class="cell-output-display">
<table class="table table-striped table-hover do-not-create-environment cell caption-top table-sm small">
<thead>
<tr class="header">
<th style="text-align: left;" data-quarto-table-cell-role="th">Domain</th>
<th style="text-align: left;" data-quarto-table-cell-role="th">Metric</th>
<th style="text-align: left;" data-quarto-table-cell-role="th">Target</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: left; width: 12em; font-weight: bold;">User adoption and engagement</td>
<td style="text-align: left; width: 22em;">Number of active patients, providers, and researchers registered</td>
<td style="text-align: left; width: 18em;">Steady growth; high retention rates across all user tiers</td>
</tr>
<tr class="even">
<td style="text-align: left; width: 12em; font-weight: bold;">Data security and privacy compliance</td>
<td style="text-align: left; width: 22em;">Number of data breaches, unauthorized access attempts; regulatory compliance rate</td>
<td style="text-align: left; width: 18em;">Zero breaches; full compliance with GDPR, HIPAA, and Israeli Privacy Protection Law</td>
</tr>
<tr class="odd">
<td style="text-align: left; width: 12em; font-weight: bold;">Research impact and utilization</td>
<td style="text-align: left; width: 22em;">Number of studies and publications using InDiGenous data; dataset access requests</td>
<td style="text-align: left; width: 18em;">Increasing citation and dataset access over time</td>
</tr>
<tr class="even">
<td style="text-align: left; width: 12em; font-weight: bold;">Patient outcomes and clinical improvements</td>
<td style="text-align: left; width: 22em;">Reduction in adverse drug reactions; improvement in treatment efficacy indicators</td>
<td style="text-align: left; width: 18em;">Measurable reduction in preventable adverse events linked to pharmacogenomics</td>
</tr>
<tr class="odd">
<td style="text-align: left; width: 12em; font-weight: bold;">Reproductive and family planning use</td>
<td style="text-align: left; width: 22em;">Usage rate of GD for reproductive counseling; satisfaction with genetic counseling</td>
<td style="text-align: left; width: 18em;">High satisfaction scores; increasing uptake in genetic counseling workflows</td>
</tr>
<tr class="even">
<td style="text-align: left; width: 12em; font-weight: bold;">PH contributions</td>
<td style="text-align: left; width: 22em;">Number of PH studies using aggregated GD; policies informed by InDiGenous data</td>
<td style="text-align: left; width: 18em;">Demonstrable policy impact at Ministry of Health level</td>
</tr>
</tbody>
</table>
</div>
</div>
</figure>
</div>
</div>
<section id="user-adoption-and-engagement" class="level3">
<h3 class="anchored" data-anchor-id="user-adoption-and-engagement">1. User adoption and engagement</h3>
<p>High <em>InDiGenous</em> adoption rates will reflect trust in the system and satisfaction with its functionality. Patient adoption will indicate acceptance of the genomic ID concept; provider engagement will demonstrate clinical utility; researcher uptake will confirm the value of the governed data access framework. User registration logs, activity monitoring, and periodic satisfaction surveys will provide the measurement basis.</p>
</section>
<section id="data-security-and-privacy-compliance" class="level3">
<h3 class="anchored" data-anchor-id="data-security-and-privacy-compliance">2. Data security and privacy compliance</h3>
<p>Zero or near-zero security incidents are the baseline expectation, not an aspirational target — given the sensitivity of GD. Regular independent security audits, real-time access log monitoring, and formal compliance assessments against GDPR, HIPAA, and Israeli Privacy Protection Law will provide ongoing verification.</p>
</section>
<section id="research-impact-and-utilization" class="level3">
<h3 class="anchored" data-anchor-id="research-impact-and-utilization">3. Research impact and utilization</h3>
<p>Growing research <em>InDiGenous</em> utilization will demonstrates the system’s contribution to genomic and epidemiological science. Dataset request logs, publication tracking, and institutional partnership records will provide measurable evidence of research impact.</p>
</section>
<section id="patient-outcomes-and-clinical-improvements" class="level3">
<h3 class="anchored" data-anchor-id="patient-outcomes-and-clinical-improvements">4. Patient outcomes and clinical improvements</h3>
<p>These metrics will require linkage between <em>InDiGenous</em> access events and clinical outcome data — a function that the EHR integration layer makes technically feasible. Healthcare providers will report on treatment success rates and adverse event frequencies in GD-informed versus non-informed care episodes.</p>
</section>
<section id="reproductive-and-family-planning-use" class="level3">
<h3 class="anchored" data-anchor-id="reproductive-and-family-planning-use">5. Reproductive and family planning use</h3>
<p>This metric is particularly relevant in the Israeli context, where carrier screening for founder-population-specific recessive disorders is culturally and clinically established. Patient surveys and genetic counseling service records will provide the measurement basis.</p>
</section>
<section id="ph-contributions" class="level3">
<h3 class="anchored" data-anchor-id="ph-contributions">6. PH contributions</h3>
<p>PH agencies will track dataset use in epidemiological studies, health campaigns, and policy documents. The ultimate indicator is demonstrable policy impact — screening program design, population health intervention targeting, or national health strategy informed by <em>InDiGenous</em>-derived evidence.</p>
</section>
</section>
<section id="vii.-legal-and-ethical-framework" class="level2">
<h2 class="anchored" data-anchor-id="vii.-legal-and-ethical-framework">VII. Legal and ethical framework</h2>
<p>GD occupy a unique position in privacy law. Unlike most personal data, GD are:</p>
<ul>
<li><p>Simultaneously individual and familial — a person’s genome implicates biological relatives who have never consented to GD collection.</p></li>
<li><p>Permanent — a compromised genome, unlike a compromised password, cannot be changed.</p></li>
<li><p>Predictive — they reveal future health probabilities that carry implications for insurance, employment, and personal relationships.</p></li>
</ul>
<p>These properties demand a legal and ethical framework specifically designed for GD, not merely an extension of general personal data protection.</p>
<section id="applicable-legal-frameworks" class="level3">
<h3 class="anchored" data-anchor-id="applicable-legal-frameworks">Applicable legal frameworks</h3>
<p><em>InDiGenous</em> will operate at the intersection of three regulatory domains:</p>
<ol type="1">
<li>International frameworks:</li>
</ol>
<ul>
<li><p><strong><em>GDPR (EU General Data Protection Regulation, 2016):</em></strong> Classifies <strong><em>GD</em></strong> as a special category requiring explicit consent, data minimization, and the right to erasure. While Israeli law is not directly subject to GDPR, alignment with it is strategically important for international research collaboration and data sharing.</p></li>
<li><p><strong><em>HIPAA (US Health Insurance Portability and Accountability Act, 1996):</em></strong> Establishes standards for protected health information, including GD, in the US context. Relevant for collaborations with American research institutions and for benchmarking security standards.</p></li>
<li><p><strong><em>GA4GH (Global Alliance for Genomics and Health) Framework for Responsible Sharing of Genomic and Health-Related Data:</em></strong> The de facto international standard for governed GD sharing in research contexts. <em>InDiGenous</em> will adopt GA4GH principles for its research access tier.</p></li>
</ul>
<ol start="2" type="1">
<li>Israeli national framework:</li>
</ol>
<ul>
<li><p><strong><em>Privacy Protection Law (1981) and Privacy Protection Regulations (Information Security, 2017):</em></strong> Israel’s primary personal data protection legislation. Establishes data subject rights, controller obligations, and security requirements. Predates the genomic era and does not address heritable data specifically — a legislative gap that <em>InDiGenous</em> must navigate through internal governance until dedicated genomic privacy legislation is enacted.</p></li>
<li><p><strong><em>Patient Rights Law (1996):</em></strong> Establishes informed consent as the basis for all medical data use. The consent architecture of <em>InDiGenous</em> is built on this foundation.</p></li>
<li><p><strong><em>National Biometric Database Law (2009, amended 2017):</em></strong> Establishes the legal precedent for national-scale sensitive biometric data collection and governance in Israel — the closest existing model for the InDiGenous national ID layer.</p></li>
<li><p><strong><em>Genetic Information Law (2000):</em></strong> Prohibits genetic discrimination in employment and insurance and regulates genetic testing consent. Directly applicable to <em>InDiGenous</em> and its clinical use tier.</p></li>
</ul>
</section>
<section id="consent-architecture" class="level3">
<h3 class="anchored" data-anchor-id="consent-architecture">Consent architecture</h3>
<p>The consent model of <em>InDiGenous</em> is:</p>
<ul>
<li><p>Dynamic: Consent can be granted, modified, or revoked at any time. Revocation will trigger immediate access suspension and — where technically feasible — deletion of previously shared data copies.</p></li>
<li><p>Granular: Consent will be given for specific data elements, specific recipients, and specific purposes — not as a single blanket authorization.</p></li>
<li><p>Audited: Every consent decision and every access event will be logged in a tamper-evident audit trail accessible to the patient.</p></li>
</ul>
<p>The <em><a href="#fig-consent-lifecycle" class="quarto-xref">Figure&nbsp;3</a></em> illustrates the consent lifecycle within <em>InDiGenous</em>.</p>
<div class="cell">
<div id="fig-consent-lifecycle" class="cell-output-display quarto-float quarto-figure quarto-figure-center anchored">
<figure class="quarto-float quarto-float-fig figure">
<div aria-describedby="fig-consent-lifecycle-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
<div class="DiagrammeR html-widget html-fill-item" id="htmlwidget-43d401a20c74664ceef8" style="width:100%;height:464px;"></div>
<script type="application/json" data-for="htmlwidget-43d401a20c74664ceef8">{"x":{"diagram":"graph TD\n    A((Patient)) -->|Initiates| B[Consent Registration]\n    B --> C{Consent Decision}\n    C -->|Grant| D[Access Authorized]\n    C -->|Deny| E[Access Blocked]\n    D --> F[Access Event Logged]\n    F --> G[Audit Trail]\n    G -->|Visible to patient| A\n    A -->|Modifies| H[Consent Update]\n    H --> C\n    A -->|Revokes| I[Consent Revocation]\n    I --> J[Access Suspended]\n    J --> G\n\n    style A fill:#2166ac,color:#ffffff,stroke:#2166ac\n    style C fill:#f4a736,color:#000000,stroke:#e08010\n    style E fill:#d73027,color:#ffffff,stroke:#d73027\n    style J fill:#d73027,color:#ffffff,stroke:#d73027\n    style G fill:#c2a5cf,color:#000000,stroke:#762a83\n    style B fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style D fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style F fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style H fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style I fill:#e8f4f8,color:#000000,stroke:#4393c3\n"},"evals":[],"jsHooks":[]}</script>
</div>
<figcaption class="quarto-float-caption-bottom quarto-float-caption quarto-float-fig" id="fig-consent-lifecycle-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
Figure&nbsp;3: Consent lifecycle within InDiGenous
</figcaption>
</figure>
</div>
</div>
</section>
<section id="surveillance-risk-mitigation" class="level3">
<h3 class="anchored" data-anchor-id="surveillance-risk-mitigation">Surveillance risk mitigation</h3>
<p>The inclusion of forensic and national security access tiers in <em>InDiGenous</em> raises legitimate concerns about the potential for genomic surveillance — the use of a health data system as an instrument of population monitoring or targeted identification beyond its stated purpose.</p>
<p>These concerns are addressed through structural separation rather than policy alone:</p>
<ul>
<li><p>Separate legal authorization pathway: Forensic and security tier access will require external judicial or ministerial authorization, independent of the patient consent engine. The system cannot be self-authorized by any internal user for extended-use access.</p></li>
<li><p>Independent audit logging: Extended-use access events will be logged in a separate audit system, monitored by an independent oversight body rather than the system operator.</p></li>
<li><p>Purpose limitation: Access requests must specify the legal basis, the specific data elements requested, and the authorized purpose. Bulk or speculative access will be technically prevented by the access control architecture.</p></li>
<li><p>Parliamentary oversight: The legal framework governing extended-use access will be subject to Knesset oversight, ensuring democratic accountability for the security tier.</p></li>
</ul>
<p>These safeguards reflect a core design principle: <strong><em>InDiGenous</em></strong> is a health data system with governed extended-use capabilities — not a surveillance system with a health data layer. The distinction is architectural, not merely rhetorical.</p>
</section>
<section id="the-legislative-gap" class="level3">
<h3 class="anchored" data-anchor-id="the-legislative-gap">The legislative gap</h3>
<p>Israel currently lacks dedicated GD governance legislation. The <em>InDiGenous</em> proposal implicitly calls for its enactment — a law that addresses heritable data sensitivity, multigenerational consent implications, the right to genomic non-disclosure, and the specific governance requirements of a national genomic ID system. Until such legislation exists, <em>InDiGenous</em> will operate under the existing Privacy Protection Law framework, supplemented by internal governance policies aligned with GDPR and GA4GH standards.</p>
<p>Engagement with the Ministry of Justice, the Ministry of Health, and the Privacy Protection Authority in the development of that legislation is a prerequisite for <em>InDiGenous</em> implementation at national scale.</p>
</section>
</section>
<section id="viii.-implementation-roadmap" class="level2">
<h2 class="anchored" data-anchor-id="viii.-implementation-roadmap">VIII. Implementation roadmap</h2>
<p><strong><em>InDiGenous</em></strong> is not conceived as a single deployment but as a phased national infrastructure project. Each phase builds on the previous, expanding scope while managing technical, legal, and adoption risks incrementally.</p>
<p>The <em><a href="#fig-roadmap" class="quarto-xref">Figure&nbsp;4</a></em> and <em><a href="#tbl-roadmap" class="quarto-xref">Table&nbsp;3</a></em> present the three-phase roadmap as a sequential process with defined milestones.</p>
<div class="cell">
<div id="fig-roadmap" class="cell-output-display quarto-float quarto-figure quarto-figure-center anchored">
<figure class="quarto-float quarto-float-fig figure">
<div aria-describedby="fig-roadmap-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
<div class="DiagrammeR html-widget html-fill-item" id="htmlwidget-05030f6c94afc9247d01" style="width:100%;height:464px;"></div>
<script type="application/json" data-for="htmlwidget-05030f6c94afc9247d01">{"x":{"diagram":"graph LR\n    A[Phase 1 - Foundation] --> B[Phase 2 - Integration]\n    B --> C[Phase 3 - Expansion]\n    A --> A1[Pilot repository at Carmel MC]\n    A --> A2[Legal framework development]\n    A --> A3[Core consent engine]\n    B --> B1[EHR integration via HL7 FHIR]\n    B --> B2[HMO linkage - Clalit, Maccabi, etc.]\n    B --> B3[PH research module]\n    C --> C1[National ID linkage]\n    C --> C2[Forensic and security tier]\n    C --> C3[International research access]\n\n    style A fill:#1a9850,color:#ffffff,stroke:#1a9850\n    style B fill:#2166ac,color:#ffffff,stroke:#2166ac\n    style C fill:#762a83,color:#ffffff,stroke:#762a83\n    style A1 fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style A2 fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style A3 fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style B1 fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style B2 fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style B3 fill:#e8f4f8,color:#000000,stroke:#4393c3\n    style C1 fill:#f7f7f7,color:#000000,stroke:#999999\n    style C2 fill:#f7f7f7,color:#000000,stroke:#999999\n    style C3 fill:#f7f7f7,color:#000000,stroke:#999999\n"},"evals":[],"jsHooks":[]}</script>
</div>
<figcaption class="quarto-float-caption-bottom quarto-float-caption quarto-float-fig" id="fig-roadmap-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
Figure&nbsp;4: InDiGenous implementation roadmap
</figcaption>
</figure>
</div>
</div>
<div class="cell">
<div id="tbl-roadmap" class="cell quarto-float quarto-figure quarto-figure-center anchored">
<figure class="quarto-float quarto-float-tbl figure">
<figcaption class="quarto-float-caption-top quarto-float-caption quarto-float-tbl" id="tbl-roadmap-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
Table&nbsp;3: InDiGenous implementation roadmap across three phases
</figcaption>
<div aria-describedby="tbl-roadmap-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
<div class="cell-output-display">
<table class="table table-striped table-hover do-not-create-environment cell caption-top table-sm small">
<thead>
<tr class="header">
<th style="text-align: left;" data-quarto-table-cell-role="th"></th>
<th style="text-align: left;" data-quarto-table-cell-role="th">Phase 1: Foundation (Years 1–2)</th>
<th style="text-align: left;" data-quarto-table-cell-role="th">Phase 2: Integration (Years 3–5)</th>
<th style="text-align: left;" data-quarto-table-cell-role="th">Phase 3: Expansion (Years 6–10)</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: left; width: 10em; font-weight: bold;">Technical</td>
<td style="text-align: left; width: 20em;">Core repository; consent interface (HE/AR/EN); pharmacogenomic alert module at Carmel MC pilot; HL7 FHIR / VCF / GA4GH DRS alignment.</td>
<td style="text-align: left; width: 20em;">FHIR API integration with all four HMOs; pharmacogenomic alerts active across HMO workflows; PH research module operational; cross-institutional GD portability.</td>
<td style="text-align: left; width: 20em;">National ID linkage via Ministry of Interior registry; forensic and security tier under judicial authorization; international research access (GA4GH Passport); 50-year archiving infrastructure.</td>
</tr>
<tr class="even">
<td style="text-align: left; width: 10em; font-weight: bold;">Legal and governance</td>
<td style="text-align: left; width: 20em;">Engagement with Ministry of Justice and Privacy Protection Authority; internal governance policy (GDPR / GA4GH aligned); ethics committee approval; data access agreement templates.</td>
<td style="text-align: left; width: 20em;">Dedicated GD governance law enacted or in advanced legislative process; data access agreements with ≥ 3 academic institutions; independent security audit published.</td>
<td style="text-align: left; width: 20em;">GD governance law fully operational; parliamentary oversight of extended-use tier; bilateral agreements with international genomic consortia.</td>
</tr>
<tr class="odd">
<td style="text-align: left; width: 10em; font-weight: bold;">Success criteria</td>
<td style="text-align: left; width: 20em;">Pilot repository operational; zero security incidents; legislative engagement formally initiated.</td>
<td style="text-align: left; width: 20em;">Active users across all HMOs; ≥ 1 published PH study using InDiGenous data; measurable reduction in pharmacogenomic adverse events.</td>
<td style="text-align: left; width: 20em;">National HMO and hospital coverage; forensic tier operational with documented legal framework; GA4GH-compliant national GD infrastructure recognized.</td>
</tr>
</tbody>
</table>
</div>
</div>
</figure>
</div>
</div>
<ol type="1">
<li><p>Foundation (years 1–2): The first phase will establish the technical and legal core of <em>InDiGenous</em> at pilot scale, without national deployment.</p></li>
<li><p>Integration (years 3–5): The second phase will scale <em>InDiGenous</em> from pilot to regional deployment, with full EHR integration and activation of the PH research module.</p></li>
<li><p>Expansion (years 6–10): The third phase will achieve national scale and activate the extended-use tiers — national ID linkage, forensic and security access, and international research collaboration.</p></li>
</ol>
<p>The phased approach serves double purpose beyond risk management: it generates evidence at each stage that justifies the next and builds the institutional trust — among patients, clinicians, researchers, and regulators — that a national genomic ID system requires before it can function at scale.</p>
<hr>
</section>
<section id="references" class="level2">
<h2 class="anchored" data-anchor-id="references">References</h2>
<section id="legal-and-regulatory-frameworks" class="level3">
<h3 class="anchored" data-anchor-id="legal-and-regulatory-frameworks">Legal and regulatory frameworks</h3>
<ul>
<li><p>General Data Protection Regulation (GDPR). (2016). European Union. https://gdpr.eu</p></li>
<li><p>Health Insurance Portability and Accountability Act (HIPAA). (1996). U.S. Department of Health and Human Services. https://www.hhs.gov/hipaa</p></li>
<li><p>Privacy Protection Law. (1981). State of Israel.</p></li>
<li><p>Privacy Protection Regulations (Information Security). (2017). State of Israel.</p></li>
<li><p>Patient Rights Law. (1996). State of Israel.</p></li>
<li><p>Genetic Information Law. (2000). State of Israel.</p></li>
<li><p>National Biometric Database Law. (2009, amended 2017). State of Israel.</p></li>
</ul>
</section>
<section id="technical-standards" class="level3">
<h3 class="anchored" data-anchor-id="technical-standards">Technical standards</h3>
<ul>
<li><p>HL7 International. (2023). HL7 FHIR Release 5. https://hl7.org/fhir</p></li>
<li><p>GA4GH Framework for Responsible Sharing of Genomic and Health-Related Data. (2021). Global Alliance for Genomics and Health. https://www.ga4gh.org</p></li>
<li><p>CPIC Guidelines. (2023). Clinical Pharmacogenomics Implementation Consortium. https://cpicpgx.org</p></li>
<li><p>ACMG Variant Classification Standards. (2023). American College of Medical Genetics and Genomics. https://www.acmg.net</p></li>
</ul>
<hr>
</section>
</section>
<section id="appendices" class="level2">
<h2 class="anchored" data-anchor-id="appendices">Appendices</h2>
<section id="appendix-a-patient-access-control-guide" class="level3">
<h3 class="anchored" data-anchor-id="appendix-a-patient-access-control-guide">Appendix A: Patient access control guide</h3>
<p>A step-by-step reference for patients managing GD permissions within <em>InDiGenous</em> (<em><a href="#tbl-access-guide" class="quarto-xref">Table&nbsp;4</a></em>).</p>
<div class="cell">
<div id="tbl-access-guide" class="cell quarto-float quarto-figure quarto-figure-center anchored">
<figure class="quarto-float quarto-float-tbl figure">
<figcaption class="quarto-float-caption-top quarto-float-caption quarto-float-tbl" id="tbl-access-guide-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
Table&nbsp;4: Patient access control guide: step-by-step permission management
</figcaption>
<div aria-describedby="tbl-access-guide-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
<div class="cell-output-display">
<table class="table table-striped table-hover do-not-create-environment cell caption-top table-sm small">
<thead>
<tr class="header">
<th style="text-align: center;" data-quarto-table-cell-role="th">Step</th>
<th style="text-align: left;" data-quarto-table-cell-role="th">Action</th>
<th style="text-align: left;" data-quarto-table-cell-role="th">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: center; width: 4em; font-weight: bold;">1</td>
<td style="text-align: left; width: 12em;">Open the consent control panel</td>
<td style="text-align: left; width: 34em;">Log into the InDiGenous patient portal (web or mobile) and navigate to the Consent Control Panel.</td>
</tr>
<tr class="even">
<td style="text-align: center; width: 4em; font-weight: bold;">2</td>
<td style="text-align: left; width: 12em;">Select data elements to share</td>
<td style="text-align: left; width: 34em;">Select specific GD elements to share: e.g., pharmacogenomic profile, carrier status, hereditary risk variants, full genomic sequence. Elements not selected remain inaccessible to all parties.</td>
</tr>
<tr class="odd">
<td style="text-align: center; width: 4em; font-weight: bold;">3</td>
<td style="text-align: left; width: 12em;">Choose recipients</td>
<td style="text-align: left; width: 34em;">Designate recipients by category (treating clinician, researcher, family member, institution) and specify the permitted purpose and duration of access.</td>
</tr>
<tr class="even">
<td style="text-align: center; width: 4em; font-weight: bold;">4</td>
<td style="text-align: left; width: 12em;">Review permissions</td>
<td style="text-align: left; width: 34em;">Review the access settings for each recipient. Confirm they reflect your intentions before saving. A plain-language summary is displayed for each permission granted.</td>
</tr>
<tr class="odd">
<td style="text-align: center; width: 4em; font-weight: bold;">5</td>
<td style="text-align: left; width: 12em;">Confirm and save</td>
<td style="text-align: left; width: 34em;">Confirm and save the permission set. A notification is issued confirming the update. All future access events by designated recipients are logged and visible in your audit trail.</td>
</tr>
</tbody>
</table>
</div>
</div>
</figure>
</div>
</div>
</section>
<section id="appendix-b-applicable-data-protection-standards-comparative-summary-tbl-standards" class="level3">
<h3 class="anchored" data-anchor-id="appendix-b-applicable-data-protection-standards-comparative-summary-tbl-standards">Appendix B: Applicable data protection standards: Comparative summary (<em><a href="#tbl-standards" class="quarto-xref">Table&nbsp;5</a></em>)</h3>
<div class="cell">
<div id="tbl-standards" class="cell quarto-float quarto-figure quarto-figure-center anchored">
<figure class="quarto-float quarto-float-tbl figure">
<figcaption class="quarto-float-caption-top quarto-float-caption quarto-float-tbl" id="tbl-standards-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
Table&nbsp;5: Comparative summary of applicable data protection frameworks
</figcaption>
<div aria-describedby="tbl-standards-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
<div class="cell-output-display">
<table class="table table-striped table-hover do-not-create-environment cell caption-top table-sm small">
<thead>
<tr class="header">
<th style="text-align: left;" data-quarto-table-cell-role="th">Framework</th>
<th style="text-align: left;" data-quarto-table-cell-role="th">Jurisdiction</th>
<th style="text-align: left;" data-quarto-table-cell-role="th">Relevance to InDiGenous</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: left; width: 12em; font-weight: bold;">GDPR</td>
<td style="text-align: left; width: 10em;">European Union</td>
<td style="text-align: left; width: 28em;">Classifies GD as special category; explicit consent required; right to erasure; data minimization principle</td>
</tr>
<tr class="even">
<td style="text-align: left; width: 12em; font-weight: bold;">HIPAA</td>
<td style="text-align: left; width: 10em;">United States</td>
<td style="text-align: left; width: 28em;">Governs protected health information including GD; security rule sets baseline encryption and access standards</td>
</tr>
<tr class="odd">
<td style="text-align: left; width: 12em; font-weight: bold;">Israeli Privacy Protection Law</td>
<td style="text-align: left; width: 10em;">Israel</td>
<td style="text-align: left; width: 28em;">Primary Israeli personal data law; predates genomic era; supplemented by InDiGenous internal governance policy</td>
</tr>
<tr class="even">
<td style="text-align: left; width: 12em; font-weight: bold;">GA4GH Framework</td>
<td style="text-align: left; width: 10em;">International</td>
<td style="text-align: left; width: 28em;">De facto standard for governed GD sharing in research; adopted for InDiGenous research and international access tiers</td>
</tr>
<tr class="odd">
<td style="text-align: left; width: 12em; font-weight: bold;">Genetic Information Law (Israel)</td>
<td style="text-align: left; width: 10em;">Israel</td>
<td style="text-align: left; width: 28em;">Prohibits genetic discrimination; regulates consent for genetic testing; directly applicable to clinical and reproductive counseling tiers</td>
</tr>
</tbody>
</table>
</div>
</div>
</figure>
</div>
</div>
</section>
</section>

</main>
<!-- /main column -->
<script id="quarto-html-after-body" type="application/javascript">
  window.document.addEventListener("DOMContentLoaded", function (event) {
    const icon = "";
    const anchorJS = new window.AnchorJS();
    anchorJS.options = {
      placement: 'right',
      icon: icon
    };
    anchorJS.add('.anchored');
    const isCodeAnnotation = (el) => {
      for (const clz of el.classList) {
        if (clz.startsWith('code-annotation-')) {
          return true;
        }
      }
      return false;
    }
    const onCopySuccess = function(e) {
      // button target
      const button = e.trigger;
      // don't keep focus
      button.blur();
      // flash "checked"
      button.classList.add('code-copy-button-checked');
      var currentTitle = button.getAttribute("title");
      button.setAttribute("title", "Copied!");
      let tooltip;
      if (window.bootstrap) {
        button.setAttribute("data-bs-toggle", "tooltip");
        button.setAttribute("data-bs-placement", "left");
        button.setAttribute("data-bs-title", "Copied!");
        tooltip = new bootstrap.Tooltip(button,
          { trigger: "manual",
            customClass: "code-copy-button-tooltip",
            offset: [0, -8]});
        tooltip.show();
      }
      setTimeout(function() {
        if (tooltip) {
          tooltip.hide();
          button.removeAttribute("data-bs-title");
          button.removeAttribute("data-bs-toggle");
          button.removeAttribute("data-bs-placement");
        }
        button.setAttribute("title", currentTitle);
        button.classList.remove('code-copy-button-checked');
      }, 1000);
      // clear code selection
      e.clearSelection();
    }
    const getTextToCopy = function(trigger) {
      const outerScaffold = trigger.parentElement.cloneNode(true);
      const codeEl = outerScaffold.querySelector('code');
      for (const childEl of codeEl.children) {
        if (isCodeAnnotation(childEl)) {
          childEl.remove();
        }
      }
      return codeEl.innerText;
    }
    const clipboard = new window.ClipboardJS('.code-copy-button:not([data-in-quarto-modal])', {
      text: getTextToCopy
    });
    clipboard.on('success', onCopySuccess);
    if (window.document.getElementById('quarto-embedded-source-code-modal')) {
      const clipboardModal = new window.ClipboardJS('.code-copy-button[data-in-quarto-modal]', {
        text: getTextToCopy,
        container: window.document.getElementById('quarto-embedded-source-code-modal')
      });
      clipboardModal.on('success', onCopySuccess);
    }
      var localhostRegex = new RegExp(/^(?:http|https):\/\/localhost\:?[0-9]*\//);
      var mailtoRegex = new RegExp(/^mailto:/);
        var filterRegex = new RegExp('/' + window.location.host + '/');
      var isInternal = (href) => {
          return filterRegex.test(href) || localhostRegex.test(href) || mailtoRegex.test(href);
      }
      // Inspect non-navigation links and adorn them if external
     var links = window.document.querySelectorAll('a[href]:not(.nav-link):not(.navbar-brand):not(.toc-action):not(.sidebar-link):not(.sidebar-item-toggle):not(.pagination-link):not(.no-external):not([aria-hidden]):not(.dropdown-item):not(.quarto-navigation-tool):not(.about-link)');
      for (var i=0; i<links.length; i++) {
        const link = links[i];
        if (!isInternal(link.href)) {
          // undo the damage that might have been done by quarto-nav.js in the case of
          // links that we want to consider external
          if (link.dataset.originalHref !== undefined) {
            link.href = link.dataset.originalHref;
          }
        }
      }
    function tippyHover(el, contentFn, onTriggerFn, onUntriggerFn) {
      const config = {
        allowHTML: true,
        maxWidth: 500,
        delay: 100,
        arrow: false,
        appendTo: function(el) {
            return el.parentElement;