3ddd8c791bece91103a991005a13be98 335912.pdf 2ba87d1517d26f7c820be28810385080e7005c83 335912.pdf 2a35d34214885eccf9abf6a52c6b4e807a970b7d1ed6a91bf0666f194d508a5c 335912.pdf Title: Using the Observational Medical Outcomes Partnership Common Data Model for a multi-registry intensive care unit benchmarking federated analysis: lessons learned Subject: Doi: 10.1093/jamiaopen/ooaf052 JAMIA Open, 8, 4, 2025 Publication Date: 17/07/2025 Abstract Objective Federated analysis is a method that allows data analysis to be performed on similar datasets without exchanging any data, thus facilitating international research collaboration while adhering to strict privacy laws. This study aimed to evaluate the feasibility of using federated analysis to benchmark mortality in 2 critical care quality registry databases converted to the Observational Medical Outcomes Partnership (OMOP) Common Data Model (CDM), describing challenges to and recommendations for performing federated analysis on data transformed to OMOP CDM.Materials and Methods To identify as many challenges as possible and to be able to complete the benchmarking phase, a 2-step approach was taken during implementation. The first step was a naive implementation to allow challenges to surface naturally; the second step was developing solutions for the encountered challenges. Expected patient mortality risk was calculated by applying the Acute Physiology and Chronic Health Evaluation II (APACHE II) model to data from OMOP CDM databases containing adult ICU encounters between July 1, 2019 and December 31, 2022. An analysis script was developed to calculate comparable, registry level standardized mortality ratios. Challenges were recorded and categorized into predefined categories: “data preparation,” “data analysis plan,” and “data interpretation.” Challenges specific to the OMOP CDM were further categorized using published steps from an existing generic harmonization process.Results A total of 7 challenges were identified, 4 of which were related to data preparation, 1 to data analysis, and 1 to data interpretation. Out of all 7 challenges, 4 stemmed from decisions made during the implementation of OMOP CDM. Several recommended solutions were distilled from the naive approach.Discussion Federated analysis facilitated by a CDM is a feasible option for critical care quality registries. However, future analysis is influenced by decisions made during the CDM implementation process. Thus, prior publication of data dictionaries and the use of metadata to communicate data handling and data source classification during CDM implementation will improve the efficiency and accuracy of subsequent analysis. Keywords: federated analysis; global health; data standardization; OMOP CDM; APACHE II; registries; critical care Creator: Servigistics Arbortext Advanced Print Publisher 11.1.4667/W Producer: PDFlib+PDI 9.0.7p3 (C++/Win32); modified using iTextSharp.LGPLv2.Core 3.7.4.0 CreationDate: Mon Jul 21 14:42:26 2025 CEST ModDate: Thu Sep 10 13:50:27 2026 CEST Custom Metadata: yes Metadata Stream: yes Tagged: yes UserProperties: no Suspects: no Form: none JavaScript: no Pages: 13 Encrypted: no Page size: 595.276 x 782.362 pts Page rot: 0 File size: 1061067 bytes Optimized: no PDF version: 1.5 name type encoding emb sub uni object ID ------------------------------------ ----------------- ---------------- --- --- --- --------- NPHQBZ+UniversLTStd-Cn Type 1C Custom yes yes yes 32 0 WPHHTR+UniversLTStd-Bold Type 1C Custom yes yes yes 33 0 TeX_CM_Maths_Symbols Type 1 Builtin yes no yes 151 0 TeX_CM_Roman Type 1 Builtin yes no yes 152 0 FEMLSI+UniversLTStd-Light Type 1C Custom yes yes yes 34 0 ORFWHC+SabonLTPro-Bold Type 1C Custom yes yes yes 68 0 NOZKXQ+SabonLTPro-Roman Type 1C Custom yes yes yes 35 0 QKIUFU+STIX-Regular Type 1C Custom yes yes yes 248 0 JYACQP+UniversLTStd-CnObl Type 1C Custom yes yes yes 977 0 AWQJSA+UniversLTStd-BoldCn Type 1C Custom yes yes yes 36 0 TELNVC+ArialMT TrueType WinAnsi yes yes no 1 0 BPSJFD+UniversLTStd Type 1C Custom yes yes yes 37 0 KRNCCE+UniversLTStd-Obl Type 1C Custom yes yes yes 38 0 LJYCXQ+SabonLTPro-Italic Type 1C Custom yes yes yes 94 0 WP-Phonetic Type 1 Builtin yes no yes 175 0 Jhove (Rel. 1.28.0, 2023-05-18) Date: 2026-09-11 04:20:33 CEST RepresentationInformation: 335912.pdf ReportingModule: PDF-hul, Rel. 1.12.4 (2023-03-16) LastModified: 2026-09-10 13:50:44 CEST Size: 1061067 Format: PDF Version: 1.5 Status: Well-Formed, but not valid SignatureMatches: PDF-hul ErrorMessage: Invalid indirect destination - referenced object 'booaf052-B23' cannot be found ID: PDF-HUL-149 ErrorMessage: Invalid indirect destination - referenced object 'booaf052-B8' cannot be found ID: PDF-HUL-149 ErrorMessage: Invalid indirect destination - referenced object 'booaf052-B34' cannot be found ID: PDF-HUL-149 ErrorMessage: Invalid indirect destination - referenced object 'booaf052-B20' cannot be found ID: PDF-HUL-149 ErrorMessage: Invalid indirect destination - referenced object 'booaf052-B19' cannot be found ID: PDF-HUL-149 ErrorMessage: Invalid indirect destination - referenced object 'booaf052-B44' cannot be found ID: PDF-HUL-149 ErrorMessage: Invalid indirect destination - referenced object 'booaf052-B18' cannot be found ID: PDF-HUL-149 ErrorMessage: Invalid indirect destination - referenced object 'booaf052-B12' cannot be found ID: PDF-HUL-149 ErrorMessage: edu.harvard.hul.ois.jhove.module.pdf.PdfInvalidException: Invalid indirect destination - referenced object 'booaf052-B34' cannot be found ID: PDF-HUL-122 Offset: 749069 ErrorMessage: edu.harvard.hul.ois.jhove.module.pdf.PdfInvalidException: Invalid indirect destination - referenced object 'booaf052-B8' cannot be found ID: PDF-HUL-122 Offset: 749069 ErrorMessage: edu.harvard.hul.ois.jhove.module.pdf.PdfInvalidException: Invalid indirect destination - referenced object 'booaf052-B18' cannot be found ID: PDF-HUL-122 Offset: 749069 ErrorMessage: edu.harvard.hul.ois.jhove.module.pdf.PdfInvalidException: Invalid indirect destination - referenced object 'booaf052-B19' cannot be found ID: PDF-HUL-122 Offset: 749069 ErrorMessage: edu.harvard.hul.ois.jhove.module.pdf.PdfInvalidException: Invalid indirect destination - referenced object 'booaf052-B44' cannot be found ID: PDF-HUL-122 Offset: 749069 ErrorMessage: edu.harvard.hul.ois.jhove.module.pdf.PdfInvalidException: Invalid indirect destination - referenced object 'booaf052-B12' cannot be found ID: PDF-HUL-122 Offset: 749069 ErrorMessage: edu.harvard.hul.ois.jhove.module.pdf.PdfInvalidException: Invalid indirect destination - referenced object 'booaf052-B20' cannot be found ID: PDF-HUL-122 Offset: 749069 ErrorMessage: edu.harvard.hul.ois.jhove.module.pdf.PdfInvalidException: Invalid indirect destination - referenced object 'booaf052-B23' cannot be found ID: PDF-HUL-122 Offset: 749069 MIMEtype: application/pdf Profile: Tagged PDF PDFMetadata: Objects: 1042 FreeObjects: 1 IncrementalUpdates: 0 DocumentCatalog: ViewerPreferences: HideToolbar: false HideMenubar: false HideWindowUI: false FitWindow: false CenterWindow: false DisplayDocTitle: true NonFullScreenPageMode: UseNone Direction: L2R ViewArea: CropBox ViewClip: CropBox PrintArea: CropBox PageClip: CropBox PageLayout: SinglePage PageMode: UseOutlines Language: en Outlines: Item: Title: Active Content List Destination: mkchap_artid Children: Item: Title: Objective Destination: mkchap5__sec Item: Title: Materials and methods Destination: mkchap6__sec Item: Title: Results Destination: mkchap14__sec Item: Title: Discussion Destination: mkchap23__sec Item: Title: Acknowledgments Destination: mkchap24_ack1_ack Item: Title: Author contributions Destination: mkchap24__sec Item: Title: Supplementary material Destination: mkchap25__sec Item: Title: Funding Destination: mkchap26__sec Item: Title: Conflicts of interest Destination: mkchap27__sec Item: Title: Data availability Destination: mkchap28__sec Item: Title: Ethics approval Destination: mkchap29__sec Item: Title: References Destination: mkchap30_ref1_ref-list Info: Title: Using the Observational Medical Outcomes Partnership Common Data Model for a multi-registry intensive care unit benchmarking federated analysis: lessons learned Subject: Doi: 10.1093/jamiaopen/ooaf052 JAMIA Open, 8, 4, 2025 Publication Date: 17/07/2025 Abstract Objective Federated analysis is a method that allows data analysis to be performed on similar datasets without exchanging any data, thus facilitating international research collaboration while adhering to strict privacy laws. This study aimed to evaluate the feasibility of using federated analysis to benchmark mortality in 2 critical care quality registry databases converted to the Observational Medical Outcomes Partnership (OMOP) Common Data Model (CDM), describing challenges to and recommendations for performing federated analysis on data transformed to OMOP CDM.Materials and Methods To identify as many challenges as possible and to be able to complete the benchmarking phase, a 2-step approach was taken during implementation. The first step was a naive implementation to allow challenges to surface naturally; the second step was developing solutions for the encountered challenges. Expected patient mortality risk was calculated by applying the Acute Physiology and Chronic Health Evaluation II (APACHE II) model to data from OMOP CDM databases containing adult ICU encounters between July 1, 2019 and December 31, 2022. An analysis script was developed to calculate comparable, registry level standardized mortality ratios. Challenges were recorded and categorized into predefined categories: “data preparation,” “data analysis plan,” and “data interpretation.” Challenges specific to the OMOP CDM were further categorized using published steps from an existing generic harmonization process.Results A total of 7 challenges were identified, 4 of which were related to data preparation, 1 to data analysis, and 1 to data interpretation. Out of all 7 challenges, 4 stemmed from decisions made during the implementation of OMOP CDM. Several recommended solutions were distilled from the naive approach.Discussion Federated analysis facilitated by a CDM is a feasible option for critical care quality registries. However, future analysis is influenced by decisions made during the CDM implementation process. Thus, prior publication of data dictionaries and the use of metadata to communicate data handling and data source classification during CDM implementation will improve the efficiency and accuracy of subsequent analysis. Keywords: federated analysis; global health; data standardization; OMOP CDM; APACHE II; registries; critical care Creator: Servigistics Arbortext Advanced Print Publisher 11.1.4667/W Producer: PDFlib+PDI 9.0.7p3 (C++/Win32); modified using iTextSharp.LGPLv2.Core 3.7.4.0 CreationDate: Mon Jul 21 15:12:26 CEST 2025 ModDate: Thu Sep 10 13:50:27 CEST 2026 ID: 0xba28ca6b111602d4c708031629e3ee00, 0xd5982a60e50c56082aedec2790977452 Filters: FilterPipeline: FlateDecode FilterPipeline: DCTDecode Images: Image: NisoImageMetadata: FormatName: image/jpg CompressionScheme: JPEG ImageWidth: 1705 ImageHeight: 1113 BitsPerSample: 8 BitsPerSampleUnit: integer Image: NisoImageMetadata: FormatName: image/jpg CompressionScheme: JPEG ImageWidth: 1750 ImageHeight: 1851 BitsPerSample: 8 BitsPerSampleUnit: integer Fonts: Type1: Font: BaseFont: NPHQBZ+UniversLTStd-Cn FontSubset: true FirstChar: 1 LastChar: 67 FontDescriptor: FontName: NPHQBZ+UniversLTStd-Cn Flags: Nonsymbolic FontBBox: -166, -250, 1000, 989 FontFile3: true EncodingDictionary: BaseEncoding: WinAnsiEncoding Differences: true ToUnicode: true Font: BaseFont: WPHHTR+UniversLTStd-Bold FontSubset: true FirstChar: 1 LastChar: 59 FontDescriptor: FontName: WPHHTR+UniversLTStd-Bold Flags: Nonsymbolic, ForceBold FontBBox: -167, -250, 995, 938 FontFile3: true EncodingDictionary: BaseEncoding: WinAnsiEncoding Differences: true ToUnicode: true Font: BaseFont: FEMLSI+UniversLTStd-Light FontSubset: true FirstChar: 1 LastChar: 61 FontDescriptor: FontName: FEMLSI+UniversLTStd-Light Flags: Nonsymbolic FontBBox: -151, -250, 1000, 957 FontFile3: true EncodingDictionary: BaseEncoding: WinAnsiEncoding Differences: true ToUnicode: true Font: BaseFont: NOZKXQ+SabonLTPro-Roman FontSubset: true FirstChar: 1 LastChar: 87 FontDescriptor: FontName: NOZKXQ+SabonLTPro-Roman Flags: Nonsymbolic FontBBox: -165, -228, 1000, 976 FontFile3: true EncodingDictionary: BaseEncoding: WinAnsiEncoding Differences: true ToUnicode: true Font: BaseFont: AWQJSA+UniversLTStd-BoldCn FontSubset: true FirstChar: 1 LastChar: 24 FontDescriptor: FontName: AWQJSA+UniversLTStd-BoldCn Flags: Nonsymbolic, ForceBold FontBBox: -83, -250, 1000, 969 FontFile3: true EncodingDictionary: BaseEncoding: WinAnsiEncoding Differences: true ToUnicode: true Font: BaseFont: ORFWHC+SabonLTPro-Bold FontSubset: true FirstChar: 1 LastChar: 63 FontDescriptor: FontName: ORFWHC+SabonLTPro-Bold Flags: Nonsymbolic, ForceBold FontBBox: -163, -228, 1000, 977 FontFile3: true EncodingDictionary: BaseEncoding: WinAnsiEncoding Differences: true ToUnicode: true Font: BaseFont: BPSJFD+UniversLTStd FontSubset: true FirstChar: 1 LastChar: 36 FontDescriptor: FontName: BPSJFD+UniversLTStd Flags: Nonsymbolic FontBBox: -168, -250, 992, 947 FontFile3: true EncodingDictionary: BaseEncoding: WinAnsiEncoding Differences: true ToUnicode: true Font: BaseFont: KRNCCE+UniversLTStd-Obl FontSubset: true FirstChar: 1 LastChar: 9 FontDescriptor: FontName: KRNCCE+UniversLTStd-Obl Flags: Nonsymbolic, Italic FontBBox: -174, -272, 1145, 947 FontFile3: true EncodingDictionary: BaseEncoding: WinAnsiEncoding Differences: true ToUnicode: true Font: BaseFont: WP-Phonetic FirstChar: 32 LastChar: 178 FontDescriptor: FontName: WP-Phonetic Flags: Symbolic FontBBox: -50, -180, 1000, 720 FontFile: true ToUnicode: true Font: BaseFont: JYACQP+UniversLTStd-CnObl FontSubset: true FirstChar: 1 LastChar: 9 FontDescriptor: FontName: JYACQP+UniversLTStd-CnObl Flags: Nonsymbolic, Italic FontBBox: -172, -270, 1064, 989 FontFile3: true EncodingDictionary: BaseEncoding: WinAnsiEncoding Differences: true ToUnicode: true Font: BaseFont: TeX_CM_Maths_Symbols FirstChar: 1 LastChar: 138 FontDescriptor: FontName: TeX_CM_Maths_Symbols Flags: Symbolic FontBBox: -50, -180, 1000, 720 FontFile: true ToUnicode: true Font: BaseFont: QKIUFU+STIX-Regular FontSubset: true FirstChar: 1 LastChar: 1 FontDescriptor: FontName: QKIUFU+STIX-Regular Flags: Nonsymbolic FontBBox: -970, -486, 2208, 1023 FontFile3: true EncodingDictionary: BaseEncoding: WinAnsiEncoding Differences: true ToUnicode: true Font: BaseFont: TeX_CM_Roman FirstChar: 1 LastChar: 127 FontDescriptor: FontName: TeX_CM_Roman Flags: Symbolic FontBBox: -50, -180, 1000, 720 FontFile: true ToUnicode: true Font: BaseFont: LJYCXQ+SabonLTPro-Italic FontSubset: true FirstChar: 1 LastChar: 50 FontDescriptor: FontName: LJYCXQ+SabonLTPro-Italic Flags: Nonsymbolic, Italic FontBBox: -146, -229, 1059, 977 FontFile3: true EncodingDictionary: BaseEncoding: WinAnsiEncoding Differences: true ToUnicode: true TrueType: Font: BaseFont: TELNVC+ArialMT FontSubset: true FirstChar: 32 LastChar: 121 FontDescriptor: FontName: TELNVC+ArialMT Flags: Nonsymbolic FontBBox: -664, -324, 2000, 1039 FontFile2: true Encoding: WinAnsiEncoding XMP: uuid:ee1819f5-7b06-2af6-54ce-ebe21839d3f6 uuid:07080B28-E7A8-47FF-209A-6A40236D0178 2025-07-21T18:12:26+05:30 2026-09-10T11:50:27+00:00 Servigistics Arbortext Advanced Print Publisher 11.1.4667/W 2026-09-10T11:50:27+00:00 PDFlib+PDI 9.0.7p3 (C++/Win32); modified using iTextSharp.LGPLv2.Core 3.7.4.0 federated analysis; global health; data standardization; OMOP CDM; APACHE II; registries; critical care Using the Observational Medical Outcomes Partnership Common Data Model for a multi-registry intensive care unit benchmarking federated analysis: lessons learned Aasiyah Rashan Daniel P Püttmann Nicolette F de Keizer Dave A Dongelmans Ronald Cornet Otavio Ranzani Wangari Waweru-Siika Matthew Smith Steve Harris Abi Beane Ferishta Bakhshi-Raiez Roya Afzali Noorullah Ahmadzai Mirwais Azizi Nasibullah Barukzai Maryam Barukzay Naqibullah Danish Maliha Farooq Maryam Shamal Ghalib Owais Urhman Ghalib Rahim Mazloomyar Shoaib Mirzada Meher Negar Bahar Nadim Abdul Majid Rahimi Muhammad Dawood Safi Muhammad Hamid Rahimi Safi Guldad Khan Saifi Ahmad Zakariya Shinwary Hiranmoy Dutta Enshad Ekramullah Aniruddha Ghose Md Hassanuzzaman Muna Islam Mahabubul Alam Khondokar Md Abdur Rahim Md Harun Or Rashid Md Abdus Sattar Abdullah Abu Sayeed Sarkar Shoman Md Rezaul Hoque Tipu Rabiul Alam Md Erfan Uddin Mohammed Jashim Uddin ASM Zahed Menbeu Sultan John Amuasi Joe Bonney Moses Siaw Frimpong Mohd Shahnaz Hasan Mohd Basri Mat Nor Mohd Zulfakar Mazlan Isha Amatya Diptesh Aryal Basanta Gauli Praveen Giri Kishor Khanal Sushil Khanal Sabin Koirala Sanjay Lakhey Subekshya Luitel Hem Raj Paneru Sushila Paudel Lalit Rajbanshi Sangina Ranjit Yam Roka Pramesh Sundar Shrestha Raju Shrestha Pradeep Tiwari Wangari Waweru-Siika Madiha Hashmi Eva Hanciles Luigi Pisani Dave Thomson , Martha Alupo Adam Hewitt Smith Dennis Kakaire Herbert Kiwalya Joseph Kiwanuka Arthur Kwizera Joshua Muhanguzi Cornelius Sendagire Udara Attanayake Abi Beane Sri Darshana Arjen M Dondorp Layoni Dullewe Nilmini P Dullewe Kaumali Gimhani Judy Ann Gitahi Rashan Haniffa Pramodya Ishani Chamira Kodippily Issrah Jawad Shiekh Mohiuddin Himasha Muvindi Upule Pabasara Luigi Pisani Dilanthi Priyadarshani Disna Pujika Aasiyah Rashan Sumayyah Rashan Thalha Rashan Shoba Sathasivam Timo Tolppa Shara Udayanga Doi: 10.1093/jamiaopen/ooaf052 JAMIA Open, 8, 4, 2025 Publication Date: 17/07/2025 Abstract Objective Federated analysis is a method that allows data analysis to be performed on similar datasets without exchanging any data, thus facilitating international research collaboration while adhering to strict privacy laws. This study aimed to evaluate the feasibility of using federated analysis to benchmark mortality in 2 critical care quality registry databases converted to the Observational Medical Outcomes Partnership (OMOP) Common Data Model (CDM), describing challenges to and recommendations for performing federated analysis on data transformed to OMOP CDM.Materials and Methods To identify as many challenges as possible and to be able to complete the benchmarking phase, a 2-step approach was taken during implementation. The first step was a naive implementation to allow challenges to surface naturally; the second step was developing solutions for the encountered challenges. Expected patient mortality risk was calculated by applying the Acute Physiology and Chronic Health Evaluation II (APACHE II) model to data from OMOP CDM databases containing adult ICU encounters between July 1, 2019 and December 31, 2022. An analysis script was developed to calculate comparable, registry level standardized mortality ratios. Challenges were recorded and categorized into predefined categories: “data preparation,” “data analysis plan,” and “data interpretation.” Challenges specific to the OMOP CDM were further categorized using published steps from an existing generic harmonization process.Results A total of 7 challenges were identified, 4 of which were related to data preparation, 1 to data analysis, and 1 to data interpretation. Out of all 7 challenges, 4 stemmed from decisions made during the implementation of OMOP CDM. Several recommended solutions were distilled from the naive approach.Discussion Federated analysis facilitated by a CDM is a feasible option for critical care quality registries. However, future analysis is influenced by decisions made during the CDM implementation process. Thus, prior publication of data dictionaries and the use of metadata to communicate data handling and data source classification during CDM implementation will improve the efficiency and accuracy of subsequent analysis. © The Author(s) 2025. Published by Oxford University Press on behalf of the American Medical Informatics Association. federated analysis global health data standardization OMOP CDM APACHE II registries critical care application/pdf PStill version 1.84.42 True 3 A http://ns.adobe.com/pdf/1.3/ pdf Adobe PDF Schema internal A name object indicating whether the document has been modified to include trapping information Trapped Text http://ns.adobe.com/xap/1.0/mm/ xmpMM XMP Media Management Schema internal UUID based identifier for specific incarnation of a document InstanceID URI internal The common identifier for all versions and renditions of a document. OriginalDocumentID URI http://www.aiim.org/pdfa/ns/id/ pdfaid PDF/A ID Schema internal Part of PDF/A standard part Integer internal Amendment of PDF/A standard amd Text internal Conformance level of PDF/A standard conformance Text Pages: Page: Sequence: 1 Annotations: Annotation: Subtype: Link Rect: 133, 563, 143, 573 Flags: Print Annotation: Subtype: Link Rect: 178, 563, 183, 574 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 186, 563, 190, 574 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 299, 563, 309, 573 Flags: Print Annotation: Subtype: Link Rect: 338, 563, 342, 574 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 345, 563, 350, 574 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 352, 563, 357, 574 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 499, 563, 504, 574 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 507, 563, 511, 574 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 514, 563, 518, 574 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 207, 548, 212, 559 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 214, 548, 219, 559 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 326, 548, 331, 559 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 334, 548, 338, 559 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 450, 548, 455, 559 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 457, 548, 462, 559 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 207, 533, 211, 544 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 326, 533, 335, 544 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 408, 533, 417, 543 Flags: Print Annotation: Subtype: Link Rect: 445, 533, 449, 544 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 535, 533, 544, 544 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 193, 518, 197, 529 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 200, 518, 204, 529 Flags: Print Destination: 331 Annotation: Subtype: Link Rect: 207, 518, 211, 529 Flags: Print Destination: 331 Page: Sequence: 2 Annotations: Annotation: Subtype: Link Rect: 61, 525, 65, 534 Flags: Print Destination: 150 Annotation: Subtype: Link Rect: 68, 525, 72, 534 Flags: Print Destination: 150 Annotation: Subtype: Link Rect: 186, 477, 190, 486 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 192, 477, 196, 486 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 103, 448, 107, 457 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 110, 448, 114, 457 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 182, 290, 190, 299 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 64, 195, 72, 204 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 75, 195, 83, 204 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 72, 136, 80, 145 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 278, 47, 285, 57 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 197, 36, 205, 46 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 330, 606, 338, 615 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 342, 606, 349, 615 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 528, 572, 535, 582 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 539, 572, 546, 582 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 543, 369, 547, 378 Flags: Print Destination: 150 Annotation: Subtype: Link Rect: 515, 347, 519, 356 Flags: Print Destination: 150 Annotation: Subtype: Link Rect: 386, 291, 390, 301 Flags: Print Destination: 150 Annotation: Subtype: Link Rect: 491, 280, 499, 289 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 448, 169, 456, 179 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 481, 147, 484, 157 Flags: Print Destination: 150 Annotation: Subtype: Link Rect: 508, 59, 516, 68 Flags: Print Destination: 174 Page: Sequence: 3 Annotations: Annotation: Subtype: Link Rect: 257, 707, 264, 717 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 176, 685, 184, 694 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 76, 640, 84, 649 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 86, 640, 94, 649 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 96, 640, 104, 649 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 249, 618, 253, 627 Flags: Print Destination: 150 Annotation: Subtype: Link Rect: 66, 562, 74, 571 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 75, 550, 83, 560 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 268, 528, 272, 537 Flags: Print Destination: 150 Annotation: Subtype: Link Rect: 253, 494, 261, 503 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 76, 449, 84, 459 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 238, 271, 246, 281 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 196, 215, 204, 225 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 94, 163, 102, 172 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 105, 163, 113, 172 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 123, 48, 131, 57 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 473, 707, 481, 716 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 363, 502, 370, 512 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 329, 446, 337, 455 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 544, 446, 552, 455 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 467, 82, 475, 91 Flags: Print Destination: 174 Page: Sequence: 4 Annotations: Annotation: Subtype: Link Rect: 212, 659, 244, 669 Flags: Print Destination: 93 Annotation: Subtype: Link Rect: 251, 659, 285, 669 Flags: Print Destination: 93 Annotation: Subtype: Link Rect: 237, 638, 271, 647 Flags: Print Annotation: Subtype: Link Rect: 92, 627, 128, 636 Flags: Print Annotation: Subtype: Link Rect: 215, 616, 247, 625 Flags: Print Destination: 109 Annotation: Subtype: Link Rect: 364, 683, 395, 692 Flags: Print Destination: 115 Annotation: Subtype: Link Rect: 447, 526, 455, 536 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 457, 526, 465, 536 Flags: Print Destination: 174 Page: Sequence: 5 Page: Sequence: 6 Page: Sequence: 7 Page: Sequence: 8 Annotations: Annotation: Subtype: Link Rect: 245, 540, 253, 549 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 255, 540, 263, 549 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 110, 522, 118, 531 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 121, 522, 129, 531 Flags: Print Destination: 247 Annotation: Subtype: Link Rect: 120, 372, 152, 381 Flags: Print Destination: 109 Annotation: Subtype: Link Rect: 155, 372, 162, 381 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 171, 250, 201, 259 Flags: Print Destination: 115 Annotation: Subtype: Link Rect: 128, 216, 136, 225 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 105, 70, 113, 79 Flags: Print Destination: 247 Annotation: Subtype: Link Rect: 268, 70, 275, 79 Flags: Print Destination: 247 Annotation: Subtype: Link Rect: 278, 70, 285, 79 Flags: Print Destination: 247 Annotation: Subtype: Link Rect: 211, 59, 215, 68 Flags: Print Destination: 150 Annotation: Subtype: Link Rect: 374, 685, 382, 694 Flags: Print Destination: 247 Annotation: Subtype: Link Rect: 435, 640, 443, 649 Flags: Print Destination: 247 Annotation: Subtype: Link Rect: 327, 204, 335, 214 Flags: Print Destination: 247 Annotation: Subtype: Link Rect: 513, 48, 517, 57 Flags: Print Destination: 174 Annotation: Subtype: Link Rect: 519, 48, 527, 57 Flags: Print Destination: 247 Page: Sequence: 9 Annotations: Annotation: Subtype: Link Rect: 169, 707, 177, 717 Flags: Print Destination: 247 Page: Sequence: 10 Page: Sequence: 11 Annotations: Annotation: Subtype: Link Rect: 48, 256, 142, 265 Flags: Print Annotation: Subtype: Link Rect: 398, 604, 552, 613 Flags: Print Annotation: Subtype: Link Rect: 323, 593, 377, 602 Flags: Print Annotation: Subtype: Link Rect: 309, 554, 345, 563 Flags: Print Annotation: Subtype: Link Rect: 321, 487, 518, 496 Flags: Print Annotation: Subtype: Link Rect: 321, 448, 518, 457 Flags: Print Annotation: Subtype: Link Rect: 321, 437, 547, 446 Flags: Print Annotation: Subtype: Link Rect: 327, 426, 400, 435 Flags: Print Annotation: Subtype: Link Rect: 321, 415, 544, 424 Flags: Print Annotation: Subtype: Link Rect: 327, 403, 392, 413 Flags: Print Annotation: Subtype: Link Rect: 321, 365, 518, 374 Flags: Print Annotation: Subtype: Link Rect: 321, 326, 518, 335 Flags: Print Annotation: Subtype: Link Rect: 309, 163, 318, 171 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 348, 142, 447, 150 Flags: Print Annotation: Subtype: Link Rect: 309, 132, 318, 140 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 309, 91, 318, 99 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 309, 61, 318, 68 Flags: Print Destination: 31 Page: Sequence: 12 Annotations: Annotation: Subtype: Link Rect: 42, 690, 51, 698 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 42, 650, 51, 658 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 42, 610, 51, 618 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 42, 579, 51, 587 Flags: Print Destination: null Annotation: Subtype: Link Rect: 42, 539, 51, 547 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 42, 509, 51, 517 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 175, 499, 285, 507 Flags: Print Annotation: Subtype: Link Rect: 59, 489, 104, 497 Flags: Print Annotation: Subtype: Link Rect: 42, 479, 51, 487 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 42, 449, 51, 457 Flags: Print Destination: null Annotation: Subtype: Link Rect: 42, 419, 51, 427 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 42, 389, 51, 397 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 42, 359, 51, 367 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 42, 329, 51, 336 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 124, 318, 285, 326 Flags: Print Annotation: Subtype: Link Rect: 59, 308, 76, 316 Flags: Print Annotation: Subtype: Link Rect: 42, 298, 51, 306 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 42, 268, 51, 276 Flags: Print Destination: null Annotation: Subtype: Link Rect: 168, 258, 285, 266 Flags: Print Annotation: Subtype: Link Rect: 59, 248, 228, 256 Flags: Print Annotation: Subtype: Link Rect: 42, 238, 51, 246 Flags: Print Destination: null Annotation: Subtype: Link Rect: 42, 208, 51, 216 Flags: Print Destination: null Annotation: Subtype: Link Rect: 159, 188, 285, 196 Flags: Print Annotation: Subtype: Link Rect: 59, 178, 254, 186 Flags: Print Annotation: Subtype: Link Rect: 42, 168, 51, 176 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 59, 158, 145, 166 Flags: Print Annotation: Subtype: Link Rect: 42, 148, 51, 156 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 42, 108, 51, 116 Flags: Print Destination: null Annotation: Subtype: Link Rect: 42, 68, 51, 76 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 303, 720, 312, 728 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 439, 700, 547, 708 Flags: Print Annotation: Subtype: Link Rect: 320, 690, 455, 698 Flags: Print Annotation: Subtype: Link Rect: 303, 680, 312, 688 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 421, 670, 547, 678 Flags: Print Annotation: Subtype: Link Rect: 320, 660, 360, 668 Flags: Print Annotation: Subtype: Link Rect: 303, 650, 312, 658 Flags: Print Destination: 31 Annotation: Subtype: Link Rect: 431, 640, 541, 648 Flags: Print Annotation: Subtype: Link Rect: 303, 630, 312, 638 Flags: Print Destination: 67 Annotation: Subtype: Link Rect: 303, 610, 312, 618 Flags: Print Destination: 67 Annotation: Subtype: Link Rect: 509, 590, 547, 597 Flags: Print Annotation: Subtype: Link Rect: 320, 579, 416, 587 Flags: Print Annotation: Subtype: Link Rect: 303, 569, 312, 577 Flags: Print Destination: 67 Annotation: Subtype: Link Rect: 303, 529, 312, 537 Flags: Print Destination: 67 Annotation: Subtype: Link Rect: 473, 519, 547, 527 Flags: Print Annotation: Subtype: Link Rect: 320, 509, 435, 517 Flags: Print Annotation: Subtype: Link Rect: 303, 499, 312, 507 Flags: Print Destination: 67 Annotation: Subtype: Link Rect: 303, 479, 312, 487 Flags: Print Destination: 67 Annotation: Subtype: Link Rect: 303, 449, 312, 457 Flags: Print Destination: null Annotation: Subtype: Link Rect: 303, 399, 312, 407 Flags: Print Destination: 67 Annotation: Subtype: Link Rect: 303, 369, 312, 377 Flags: Print Destination: 67 Annotation: Subtype: Link Rect: 303, 329, 312, 337 Flags: Print Destination: 67 Annotation: Subtype: Link Rect: 342, 308, 471, 316 Flags: Print Annotation: Subtype: Link Rect: 303, 298, 312, 306 Flags: Print Destination: 67 Annotation: Subtype: Link Rect: 303, 258, 312, 266 Flags: Print Destination: 67 Annotation: Subtype: Link Rect: 303, 218, 312, 226 Flags: Print Destination: 93 Annotation: Subtype: Link Rect: 413, 198, 509, 206 Flags: Print Annotation: Subtype: Link Rect: 303, 188, 312, 196 Flags: Print Destination: 93 Annotation: Subtype: Link Rect: 419, 178, 547, 186 Flags: Print Annotation: Subtype: Link Rect: 320, 168, 335, 176 Flags: Print Annotation: Subtype: Link Rect: 303, 158, 312, 166 Flags: Print Destination: 121 Annotation: Subtype: Link Rect: 303, 98, 312, 106 Flags: Print Destination: 121 Annotation: Subtype: Link Rect: 355, 78, 526, 85 Flags: Print Annotation: Subtype: Link Rect: 303, 68, 312, 76 Flags: Print Destination: null Annotation: Subtype: Link Rect: 497, 57, 547, 65 Flags: Print Annotation: Subtype: Link Rect: 320, 47, 470, 55 Flags: Print Page: Sequence: 13 Annotations: Annotation: Subtype: Link Rect: 48, 720, 57, 728 Flags: Print Destination: 121 Annotation: Subtype: Link Rect: 65, 700, 227, 708 Flags: Print Annotation: Subtype: Link Rect: 48, 690, 57, 698 Flags: Print Destination: 121 Annotation: Subtype: Link Rect: 195, 680, 291, 688 Flags: Print Annotation: Subtype: Link Rect: 65, 670, 111, 678 Flags: Print Annotation: Subtype: Link Rect: 48, 660, 57, 668 Flags: Print Destination: 121 Annotation: Subtype: Link Rect: 48, 630, 57, 638 Flags: Print Destination: 121 Annotation: Subtype: Link Rect: 99, 620, 210, 628 Flags: Print Annotation: Subtype: Link Rect: 48, 610, 57, 618 Flags: Print Destination: 121 Annotation: Subtype: Link Rect: 172, 591, 291, 598 Flags: Print Annotation: Subtype: Link Rect: 65, 581, 189, 589 Flags: Print Annotation: Subtype: Link Rect: 309, 720, 318, 728 Flags: Print Destination: 121 Annotation: Subtype: Link Rect: 508, 710, 552, 718 Flags: Print Annotation: Subtype: Link Rect: 326, 700, 552, 708 Flags: Print Annotation: Subtype: Link Rect: 326, 690, 413, 698 Flags: Print Annotation: Subtype: Link Rect: 309, 680, 318, 688 Flags: Print Destination: 121 Annotation: Subtype: Link Rect: 309, 630, 318, 638 Flags: Print Destination: 142 Checksum: 2f3657d0 Type: CRC32 Checksum: 3ddd8c791bece91103a991005a13be98 Type: MD5 Checksum: 2ba87d1517d26f7c820be28810385080e7005c83 Type: SHA-1 Checksum: 2a35d34214885eccf9abf6a52c6b4e807a970b7d1ed6a91bf0666f194d508a5c Type: SHA-256