Google Cloud FHIR Apis and Data Harmonization Kalyan Pamarthy, Marianne Slight, and Vivian Neilley, Google Cloud Healthcare

Total Page:16

File Type:pdf, Size:1020Kb

Google Cloud FHIR Apis and Data Harmonization Kalyan Pamarthy, Marianne Slight, and Vivian Neilley, Google Cloud Healthcare Google Cloud FHIR APIs and Data Harmonization Kalyan Pamarthy, Marianne Slight, and Vivian Neilley, Google Cloud Healthcare HL7 FHIR DevDays 2020, Virtual Edition US, June 15–18, 2020 | @HL7 @FirelyTeam | #fhirdevdays | www.devdays.com/us HL7®, FHIR® and the flame Design mark are the registered trademarks of Health Level Seven International and are used with permission. Kalyan Pamarthy Marianne Slight Vivian Neilley Product Manager Product Manager Solutions Engineer FHIR and HL7v2 Healthcare Analytics Healthcare & Life Sciences 2 Topics for today ● G o o g le Clo ud He a lt hc a re API & FHIR c a p a b ilit ie s ● Instructions for Let’s Build ● Google Cloud Healthcare Data Harmonization and De mo Cloud Healthcare API & Data Harmonization Related Presentations ● Let’s Build: Google Cloud FHIR APIs ● Building FHIR - based apps for Cancer Thursday, June 18th, 2:00 pm-2:4 0 p m ET referrals at the University Health Network University Health Network Tuesday, June 16th, 3:30 pm-3:4 5 p m ET ● Building Machine Learning Systems on FHIR with BigQuery and Looker Monday, June 15th, 4:15 pm-4 :30 p m ET ● Building a Real Time Machine Learning System with FHIR and a DICOM VNA Koo Foundation Sun-Yat Sen Cancer Center ● Extend Clinical Workflows using SMART (KFSYSCC) and Stratus Medicine Tuesday, June 16th, 4:45 pm-5:00 pm ET on FHIR Thursday, June 18th 4:00 pm-4 :15 p m ET 1. Google Cloud Healthcare API 5 Cloud Healthcare API Capabilities Accelerate your healthcare solution development ● Primary API surface for healthcare specific data management in the Google Clo ud Pla t fo rm . ● Fully managed, Standards based serverless, REST APIs ○ FHIR (DSTU2, STU3 a n d R4 ) ○ HL7v2 ○ DIC O M ● Value add capabilities (e.g De-Id, Data Harmonization, NLP) Healthcare API ● St o re s PHI d a t a in c o m p lia nc e wit h re g ula t io ns (e .g HIPAA) ● Integrated with other Google Cloud applications (e.g BigQuery) ● Integrated with Google Cloud components (e.g Cloud PubSub, Cloud Functions) ● Support for Smart on FHIR Apps with Apigee API Management Key Managed FHIR Server Capabilities DSTU2, STU3 & R4 Support FHIR Versions Resource Create/Read/Update/Patch/History/Delete O p e rat io ns FHIR FHIR Se a r c h Operations Patient $Everything Execute Bundle (Batch & Transaction) Cloud Healthcare IG Support & FHIR Pro file Valid at io n FHIR APIs Profiles Import & HL7v2 and CSV to FHIR transformations Export Import and Export from/to Google Cloud Storage Export to BigQuery - Streaming and Batch Access resources via FHIR Standard REST APIs Pro je c t Cloud Healthcare API Location Dataset Store (FHIR Datastore) E.g Get Patient data from a Cloud FHIR Store Le t ’s Build : G o o g le Clo ud FHIR APIs $> curl - X GET https://healthcare.googleapis.com/ v1 /projects/PROJECT_ID/ l ocat i ons/ LOCATION/ dat aset s/ DATASET_ID/ f hi r Thursday, June 18th, 2:00 St or es / FHIR_STORE_ID/Patient/1 pm-2:40 pm - H ' Aut hor i zat i on: Bear er <access - token> ' https://cloud.google.com/healthcare/docs/how-t o s/fhir Popular Use Cases ● [Cloud Native Health Apps] FHIR Se rve r & APIs as the backend for consumer and enterprise applications. E.g diabetes management, practice management systems ● [Providers] Extracting data out of EMRs and other on-prem systems into the FHIR Server and enable real-time applications and large scale data analytics. Cloud Healthcare E.g patient rounding apps, Sepsis prediction FHIR APIs ● [Payers] Implement Payer Data Access APIs for meeting CMS/ONC mandates Le t ’s Build : G o o g le Clo ud FHIR APIs Thursday, June 18th, 2:00 pm-2:40 pm cloud.google.com/healthcare G e ne ra lly Ava ila b le Build this with us on Thursday! Le t ’s Build : G o o g le Clo ud FHIR APIs Thursday, June 18th, 2:00 pm-2:40 pm 1. Gain Access to the free GCP Lab at: bit.ly/gcpfhir 2. Receive link to the lab 11 2. Google Cloud Data Harmonization 12 Data Harmonization: Clinical Sources Sources Formats Mapping Ta rg e t transformatio schemas n CSV Fie ld mappings Hist o ric a l data Terminology mappings Unit s alignment HL7v2 CSV Clinic a l e nt it y extraction St re a m ing data Mapping: Whistle Data Transformation Language Input JSON Transformatio Output JSON n library Whis t le mapping config Whistle is not FHIR Mapping Language - Generic mapping config, supports other schemas - More compact syntax - No forced profile checks - Transpiler for FML Mapping: Whistle Data Transformation Language { { "segmentId": "XAD", "use": "Work", "fields": { Transformatio "text": "55 Fruit Street Massachusetts General "1": "55 Fruit Street", Hospital Boston MA 02114 USA", "2": "Massachusetts General Hospital", n library "line": [ "3": "Boston", "55 Fruit Street" "4": "MA", ], "5": "02114", "city": "Boston", "6": "USA", "district": 100, "7": "Work", "state": "MA", "zipCode": "02114", "8": "Other geographic designation", use: XAD.7 "country": "USA", "9": "100" text: " ", XAD.1, XAD.2, XAD.3, XAD.4, "type": "physical" } XAD.5, XAD.6 => _StrJoin } line: XAD.1 => _ListOf } city: XAD.3 district: XAD.9 state: XAD.4 Sample maps: zipCode: XAD.5 - HL7v2 to FHIR for country: XAD.6 Supports repeated and nested structures, type: "physical" ADT_A0 1 a n d O RU_R0 1 terminology mapping, unit harmonization, init ially c linic al e nt it y e xt rac t io n, use r-defined - FHIR to OMOP Whist le m a p p ing c o nfig functions - OMOP to FHIR How To Run A Whistle Mapping Config Healthcare API Cloud Data Fusion OSS Dataflow Fully m a na g e d , c lo ud -native data FHIR Im p o rt API Reference Cloud Dataflow int e g rat io n se rvic e fo r b uild ing and (Apache Beam) pipeline to managing ETL and ELT data p ip e line s. convert streaming HL7v2 Cloud Whis t le Cloud messages to FHIR Storage c o nfig Healthcare With a graphical interface and a resources broad open source library of FHIR Exp o rt API preconfigured connectors and transformations, Cloud Data Fusion shifts an organization’s focus away Cloud Whis t le from code and integration to BigQuery Healthcare c o nfig insights and action. HL7v2 → FHIR API Cloud Whis t le Cloud Healthcare c o nfig Healthcare Show me! 18.
Recommended publications
  • HW&Co. Landscape Industry Reader Template
    TECHNOLOGY, MEDIA, & TELECOM QUARTERLY SOFTWARE SECTOR REVIEW │ 3Q 2016 www.harriswilliams.com Investment banking services are provided by Harris Williams LLC, a registered broker-dealer and member of FINRA and SIPC, and Harris Williams & Co. Ltd, which is authorised and regulated by the Financial Conduct Authority. Harris Williams & Co. is a trade name under which Harris Williams LLC and Harris Williams & Co. Ltd conduct business. TECHNOLOGY, MEDIA, & TELECOM QUARTERLY SOFTWARE SECTOR REVIEW │ 3Q 2016 HARRIS WILLIAMS & CO. OVERVIEW HARRIS WILLIAMS & CO. (HW&CO.) GLOBAL ADVISORY PLATFORM CONTENTS . DEAL SPOTLIGHT . M&A TRANSACTIONS – 2Q 2016 KEY FACTS . SOFTWARE M&A ACTIVITY . 25 year history with over 120 . SOFTWARE SECTOR OVERVIEWS closed transactions in the . SOFTWARE PRIVATE PLACEMENTS last 24 months OVERVIEW . SOFTWARE PUBLIC COMPARABLES . Approximately 250 OVERVIEW professionals across seven . TECHNOLOGY IPO OVERVIEW offices in the U.S. and . DEBT MARKET OVERVIEW Europe . APPENDIX: PUBLIC COMPARABLES DETAIL . Strategic relationships in India and China HW&Co. Office TMT CONTACTS Network Office UNITED STATES . 10 industry groups Jeff Bistrong Managing Director HW&CO. TECHNOLOGY, MEDIA & TELECOM (TMT) GROUP FOCUS AREAS [email protected] Sam Hendler SOFTWARE / SAAS INTERNET & DIGITAL MEDIA Managing Director [email protected] . Enterprise Software . IT and Tech-enabled . AdTech and Marketing . Digital Media and Content Services Solutions Mike Wilkins . Data and Analytics . eCommerce Managing Director . Infrastructure and . Data Center and . Consumer Internet . Mobile [email protected] Managed Services Security Software EUROPE Thierry Monjauze TMT VERTICAL FOCUS AREAS Managing Director [email protected] . Education . Fintech . Manufacturing . Public Sector and Non-Profit . Energy, Power, and . Healthcare IT . Professional Services . Supply Chain, Transportation, TO SUBSCRIBE PLEASE EMAIL: Infrastructure and Logistics *[email protected] SELECT RECENT HW&CO.
    [Show full text]
  • Starburst Enterprise on Google Cloud
    SOLUTION BRIEF Starburst Enterprise on Google Cloud The Starburst Enterprise Difference As organizations scale up, Starburst Enterprise on Google Cloud drives Available on the Google Cloud Marketplace, the better business outcomes, consistency, and reliability, delighting your data Starburst Enterprise platform is a fully supported, engineers and scientists. Teams look to Starburst Enterprise on Google Cloud production-tested, enterprise-grade distribution for expertise & constant fine-tuning that results in overall lower costs & faster of the open source Trino MPP SQL query engine. time-to-insights: Starburst integrates Google’s scalable cloud storage and computing services with a more Performance: stable, secure, efficient, and cost-effective way Includes the latest optimizations; Starburst Cached Views available for to query all your enterprise data, wherever it frequently accessed data; stable code that minimizes failed queries. resides. Leading organizations across multiple industries Connectivity rely on Starburst Enterprise and Google. 40+ supported enterprise connectors; high performance connectors for Oracle, Teradata, Snowflake, IBM DB2, Delta Lake, and many more. Analytics Anywhere Designed for the separation of storage and Security compute, Trino is ideal for querying data residing in multiple systems, from cloud data lakes to Role-based access control (via Apache Ranger); Kerberos, OKTA, LDAP legacy data warehouses. Deployed via Google integration; data encryption & masking; query auditing to see who is doing what. Kubernetes Engine (GKE), Starburst Enterprise on Google Cloud enables the user to run analytic Management queries across Google Cloud data sources and on-prem systems such as Teradata, Oracle, Enhanced tools for configuration, auto scaling, and Starburst Insights and others via Trino clusters. Within a single monitoring dashboards; easy deployment on Google platforms.
    [Show full text]
  • Google Cloud Issue Summary Multiple Products - 2020-08-19 All Dates/Times Relative to US/Pacific
    Google Cloud Issue Summary Multiple Products - 2020-08-19 All dates/times relative to US/Pacific Starting on August 19, 2020, from 20:55 to 03:30, multiple G Suite and Google Cloud Platform products experienced errors, unavailability, and delivery delays. Most of these issues involved creating, uploading, copying, or delivering content. The total incident duration was 6 hours and 35 minutes, though the impact period differed between products, and impact was mitigated earlier for most users and services. We understand that this issue has impacted our valued customers and users, and we apologize to those who were affected. DETAILED DESCRIPTION OF IMPACT Starting on August 19, 2020, from 20:55 to 03:30, Google Cloud services exhibited the following issues: ● Gmail: The Gmail service was unavailable for some users, and email delivery was delayed. About ​ 0.73% of Gmail users (both consumer and G Suite) active within the preceding seven days experienced 3 or more availability errors during the outage period. G Suite customers accounted for 27% of affected Gmail users. Additionally, some users experienced errors when adding attachments to messages. Impact on Gmail was mitigated by 03:30, and all messages delayed by this incident have been delivered. ● Drive: Some Google Drive users experienced errors and elevated latency. Approximately 1.5% of Drive ​ users (both consumer and G Suite) active within the preceding 24 hours experienced 3 or more errors during the outage period. ● Docs and Editors: Some Google Docs users experienced issues with image creation actions (for ​ example, uploading an image, copying a document with an image, or using a template with images).
    [Show full text]
  • System and Organization Controls (SOC) 3 Report Over the Google Cloud Platform System Relevant to Security, Availability, and Confidentiality
    System and Organization Controls (SOC) 3 Report over the Google Cloud Platform System Relevant to Security, Availability, and Confidentiality For the Period 1 May 2020 to 30 April 2021 Google LLC 1600 Amphitheatre Parkway Mountain View, CA, 94043 650 253-0000 main Google.com Management’s Report of Its Assertions on the Effectiveness of Its Controls Over the Google Cloud Platform System Based on the Trust Services Criteria for Security, Availability, and Confidentiality We, as management of Google LLC ("Google" or "the Company") are responsible for: • Identifying the Google Cloud Platform System (System) and describing the boundaries of the System, which are presented in Attachment A • Identifying our service commitments and system requirements • Identifying the risks that would threaten the achievement of its service commitments and system requirements that are the objectives of our System, which are presented in Attachment B • Identifying, designing, implementing, operating, and monitoring effective controls over the Google Cloud Platform System (System) to mitigate risks that threaten the achievement of the service commitments and system requirements • Selecting the trust services categories that are the basis of our assertion We assert that the controls over the System were effective throughout the period 1 May 2020 to 30 April 2021, to provide reasonable assurance that the service commitments and system requirements were achieved based on the criteria relevant to security, availability, and confidentiality set forth in the AICPA’s
    [Show full text]
  • The Book of Apigee Edge Antipatterns V2.0
    The Book of Apigee Edge Antipatterns Avoid common pitfalls, maximize the power of your APIs Version 2.0 Google Cloud ​Privileged and confidential. ​apigee 1 Contents Introduction to Antipatterns 3 What is this book about? 4 Why did we write it? 5 Antipattern Context 5 Target Audience 5 Authors 6 Acknowledgements 6 Edge Antipatterns 1. Policy Antipatterns 8 1.1. Use waitForComplete() in JavaScript code 8 1.2. Set Long Expiration time for OAuth Access and Refresh Token 13 1.3. Use Greedy Quantifiers in RegularExpressionProtection policy​ 16 1.4. Cache Error Responses 19 1.5. Store data greater than 512kb size in Cache ​24 1.6. Log data to third party servers using JavaScript policy 27 1.7. Invoke the MessageLogging policy multiple times in an API proxy​ 29 1.8. Configure a Non Distributed Quota 36 1.9. Re-use a Quota policy 38 1.10. Use the RaiseFault policy under inappropriate conditions​ 44 1.11. Access multi-value HTTP Headers incorrectly in an API proxy​ 49 1.12. Use Service Callout policy to invoke a backend service in a No Target API proxy 54 Google Cloud ​Privileged and confidential. ​apigee 2 2. Performance Antipatterns 58 2.1. Leave unused NodeJS API Proxies deployed 58 3. Generic Antipatterns 60 3.1. Invoke Management API calls from an API proxy 60 3.2. Invoke a Proxy within Proxy using custom code or as a Target 65 3.3. Manage Edge Resources without using Source Control Management 69 3.4. Define multiple virtual hosts with same host alias and port number​ 73 3.5.
    [Show full text]
  • Manpreet Singh
    MANPREET SINGH SUMMARY OF EXPERTISE ​ ​ ● 1 Year of Co-op experience at SAP as SLT/HANA Product support Engineer. ● 2+ years of full time experience in US IT firm named Cognizant as Java and ESB Developer. ● Broad understanding of Machine Learning, AI and hands on with latest developments in IoT. ● Experience in Penetration Testing, Intrusion Detection, Digital forensics and Risk Management. ● Sound Knowledge and Experience in Google API Management Platform named Apigee. ● Well acquainted with knowledge related to IT Infrastructure and SOA architecture. ● Good organizational, analytical, problem-solving skills and a great team player. ACADEMIC & PROFESSIONAL DEVELOPMENT Master of Engineering (Sep 2017 - Apr 2019) University of Victoria, Canada ​ Electrical and Computer Engineering Bachelor of Technology (Aug 2011 - May 2015) LPU, Punjab, India Electronics and Communication Engineering TECHNICAL SKILLS Enterprise Tools SAP SLT, Apigee Edge, SAG webMethods, Soap UI, Splunk, SNow Penetration Testing Tools Nessus, Zenmap, Wireshark, Hydra, Burp-suite, Metasploit Programming C++, Java, Python Database MySQL Web Development Wordpress, HTML5, CSS3 Network TCP/IP, OSI Model, WLAN/LAN technologies Operating System Windows, Linux (Kali), Mac OS, iOS, Android Interpersonal Leadership, Teamwork, Time Management, Communication WORK EXPERIENCE Software Dev QA Engineer 1 (August 2019- Present) Fortinet Technologies, Burnaby, BC Canada. ● Work as Software developer for various security interfaces. ● Work as QA engineer for testing the code in production and development. Product Support Engineer (Sept 2018 – August 2019) SAP, Vancouver, Canada SAP Landscape Transformation Replication Server (SLT) Engineer ● Worked as a SLT product support engineer; handling Configurations, Troubleshooting and Incident Handling for top SAP clients. ● Handled (VH) priority issues for real business problems using live troubleshooting sessions for Max Attention Customers like Apple, Porsche, Coca-Cola.
    [Show full text]
  • Data Warehouse Offload to Google Bigquery
    DATA WAREHOUSE OFFLOAD TO GOOGLE BIGQUERY In a world where big data presents both a major opportunity and a considerable challenge, a rigid, highly governed traditional enterprise data warehouse isn’t KEY BENEFITS OF MOVING always the best choice for processing large workloads, or for applications like TO GOOGLE BIGQUERY analytics. Google BigQuery is a lightning-fast cloud-based analytics database that lets you keep up with the growing data volumes you need to derive meaningful • Reduces costs and business value, while controlling costs and optimizing performance. shifts your investment from CAPEX to OPEX Pythian’s Data Warehouse Offload to Google BigQuery service moves your workload from an existing legacy data warehouse to a Google BigQuery data • Scales easily and on demand warehouse using our proven methodology and Google experts–starting with a fixed-cost Proof of Concept stage that will quickly demonstrate success. • Enables self-service analytics and advanced analytics GETTING STARTED The Pythian Data Warehouse Offload to Google BigQuery service follows a proven methodology and delivers a Proof of Concept (POC) that demonstrates viability and value within three to four weeks. The POC phase will follow this workflow: 1. Assess existing data warehouse environment to identify tables and up to two reports that will be offloaded in this phase 2. Provision GCP infrastructure including Cloud storage, Bastion hosts, BigQuery, and Networking 3. Implement full repeatable extract/load process for selected tables 4. Implement selected reports on BigQuery 5. Produce report PYTHIAN DELIVERS By the end of the first stage of our engagement, you can expect to have: • Working prototype on BigQuery • Up to two reports • Demonstrated analysis capabilities using one fact with five associated dimensions www.pythian.com • Report that includes: an assessment of your current setup and support you need to plan and maintain your full (including a cost analysis for BigQuery), performance/ Google BigQuery data warehouse and enterprise analytics usability analysis of POC vs.
    [Show full text]
  • Google Cloud Whitepaper
    1 Table of contents Introduction 3 The compliance landscape for UK health and social care data 4 Legislation governing UK health data 4 Overview of NHS Digital in England 6 Overview of the Use of Public Cloud Guidance 6 Overview of the DSP Toolkit 7 Google Cloud Platform information governance overview 8 Google Cloud Platform’s approach to security and data protection 8 The Shared Responsibility Model 12 How Google Cloud Platform meets NHS Information Governance requirements 13 Data Security Standard 1 13 Data Security Standard 2 20 Data Security Standard 3 22 Data Security Standard 4 22 Data Security Standard 5 25 Data Security Standard 6 26 Data Security Standard 7 29 Data Security Standard 8 31 Data Security Standard 9 32 Data Security Standard 10 33 How Google Cloud Platform helps customers meet their DSP Toolkit requirements 34 Google Cloud Platform products to help with compliance 34 Google Cloud Platform Terms of Service and Conditions 37 Additional Resources to help Google Cloud Platform customers 37 Conclusion 38 2 Disclaimer This document was last updated in O ctober 2020 a nd is for informational purposes only. Google does not intend the information or recommendations in this document to constitute legal advice. Each customer must independently evaluate its own particular use of the services as appropriate to support its legal compliance obligations. Since Google is continually improving security and other features for our customers, some of the policies, procedures, and technologies mentioned in this document may have changed. Please visit cloud.google.com/security/compliance or contact your Google Cloud Account Representative to check for updated information.
    [Show full text]
  • Cloudpools and Google Cloud Architectural Overview, Considerations, and Best Practices
    Technical White Paper Dell EMC PowerScale: CloudPools and Google Cloud Architectural overview, considerations, and best practices Abstract This white paper provides an overview of Dell EMC™ PowerScale™ CloudPools software in OneFS™ 9.1.0.0. It describes its policy-based capabilities that can reduce storage costs and optimize storage by automatically moving infrequently accessed data to Google Cloud. April 2021 H17993.3 Revisions Revisions Date Description October 2019 Initial release June 2020 Updated best practices October 2020 Updated CloudPools operations April 2021 Updated best practices Acknowledgments Author: Jason He ([email protected]) Dell EMC and the authors of this document welcome your feedback on this white paper. This document may contain certain words that are not consistent with Dell's current language guidelines. Dell plans to update the document over subsequent future releases to revise these words accordingly. This document may contain language from third party content that is not under Dell's control and is not consistent with Dell's current guidelines for Dell's own content. When such third party content is updated by the relevant third parties, this document will be revised accordingly. The information in this publication is provided “as is.” Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any software described in this publication requires an applicable software license. Copyright © 2019 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc.
    [Show full text]
  • Economic and Social Impacts of Google Cloud September 2018 Economic and Social Impacts of Google Cloud |
    Economic and social impacts of Google Cloud September 2018 Economic and social impacts of Google Cloud | Contents Executive Summary 03 Introduction 10 Productivity impacts 15 Social and other impacts 29 Barriers to Cloud adoption and use 38 Policy actions to support Cloud adoption 42 Appendix 1. Country Sections 48 Appendix 2. Methodology 105 This final report (the “Final Report”) has been prepared by Deloitte Financial Advisory, S.L.U. (“Deloitte”) for Google in accordance with the contract with them dated 23rd February 2018 (“the Contract”) and on the basis of the scope and limitations set out below. The Final Report has been prepared solely for the purposes of assessment of the economic and social impacts of Google Cloud as set out in the Contract. It should not be used for any other purposes or in any other context, and Deloitte accepts no responsibility for its use in either regard. The Final Report is provided exclusively for Google’s use under the terms of the Contract. No party other than Google is entitled to rely on the Final Report for any purpose whatsoever and Deloitte accepts no responsibility or liability or duty of care to any party other than Google in respect of the Final Report and any of its contents. As set out in the Contract, the scope of our work has been limited by the time, information and explanations made available to us. The information contained in the Final Report has been obtained from Google and third party sources that are clearly referenced in the appropriate sections of the Final Report.
    [Show full text]
  • Department of Defense Enterprise Devsecops Initiative
    Headquarters U.S. Air Force I n t e g r i t y - S e r v i c e - E x c e l l e n c e How did the Department of Defense move to Kubernetes and Istio? Mr. Nicolas Chaillan Chief Software Officer, U.S. Air Force Co-Lead, DoD Enterprise DevSecOps Initiative V2.5 – UNCLASSFIED Must Adapt to Challenges Must Rapidly Adapt To Challenges I n t e g r i t y - S e r v i c e - E x c e l l e n c e 2 Must Adapt to Challenges Work as a Team! Must Adapt To Challenges I n t e g r i t y - S e r v i c e - E x c e l l e n c e 3 Must Adapt to Challenges Work as a Team! A Large Team! Must Adapt To Challenges I n t e g r i t y - S e r v i c e - E x c e l l e n c e 4 Must Adapt to Challenges With Various TechnologiesWork as a Team! A Large Team! Must Adapt To Challenges I n t e g r i t y - S e r v i c e - E x c e l l e n c e 5 Must Adapt to Challenges With Various Technologies Work as a Team! A Large Team! Must AdaptBring To Challenges It With Us! I n t e g r i t y - S e r v i c e - E x c e l l e n c e 6 Must Adapt to Challenges With Various Technologies Work as a Team! Even To Space! A Large Team! Must AdaptBring To Challenges It With Us! I n t e g r i t y - S e r v i c e - E x c e l l e n c e 7 Must Adapt to Challenges With Various Technologies Work as a Team! To Space! A Large Team! MustWith Adapt a FewBring To Sensors! Challenges It With Us! I n t e g r i t y - S e r v i c e - E x c e l l e n c e 8 With Their Help! Must Adapt to Challenges With Various Technologies Work as a Team! To Space! A Large Team! MustWith Adapt a FewBring To Sensors! Challenges It With Us! I n t e g r i t y - S e r v i c e - E x c e l l e n c e 9 What is the DoD Enterprise DevSecOps Initiative? Joint Program with OUSD(A&S), DoD CIO, U.S.
    [Show full text]
  • Frequently Asked Questions for Google Bigquery Connector
    Frequently Asked Questions for Google BigQuery Connector © Copyright Informatica LLC 2017, 2021. Informatica, the Informatica logo, and Informatica Cloud are trademarks or registered trademarks of Informatica LLC in the United States and many jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at https:// www.informatica.com/trademarks.html. Abstract This article describes frequently asked questions about using Google BigQuery Connector to read data from and write data to Google BigQuery. Supported Versions • Cloud Data Integration Table of Contents General Questions............................................................ 2 Performance Tuning Questions................................................... 5 General Questions What is Google Cloud Platform? Google Cloud Platform is a set of public cloud computing services offered by Google. It provides a range of hosted services for compute, storage, and application development that run on Google hardware. Google Cloud Platform services can be accessed by software developers, cloud administrators, and other enterprise IT professionals over the public internet or through a dedicated network connection. Google Cloud Platform provides Google BigQuery to perform data analytics on large datasets. How can I access Google Cloud Platform? You must create a Google service account to access Google Cloud Platform. To create a Google service account, click the following URL: https://cloud.google.com/ What are the permissions required for the Google service
    [Show full text]