[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-18。"],[[["\u003cp\u003eThe Cloud Healthcare API provides a cloud-based solution for managing healthcare data, supporting standards like DICOM, FHIR (DSTU2, STU3, R4), and HL7v2.\u003c/p\u003e\n"],["\u003cp\u003eIt offers secure storage and retrieval of healthcare data, including ePHI, and facilitates data integration with existing healthcare systems.\u003c/p\u003e\n"],["\u003cp\u003eThe API is compliant with industry security and privacy standards such as ISO 27001, ISO 27017, ISO 27018, PCI DSS, and HIPAA, ensuring data protection and regulatory adherence.\u003c/p\u003e\n"],["\u003cp\u003eIt supports bulk import/export of DICOM and FHIR data to Cloud Storage and export of FHIR resources and DICOM store metadata to BigQuery for advanced analytics.\u003c/p\u003e\n"],["\u003cp\u003eThe Cloud Healthcare API allows for data de-identification and provides high performance, availability, durability, and auditability through Google Cloud's infrastructure.\u003c/p\u003e\n"]]],[],null,["# Overview of the Cloud Healthcare API\n\nThe Cloud Healthcare API provides industry-standard protocols and formats\nfor ingesting, storing, analyzing, and integrating healthcare data with\ncloud-based applications. The API supports the following applications:\n\n- Healthcare machine learning applications\n- Data-level integration of healthcare systems\n- Secure storage and retrieval of healthcare and life science data, including electronic protected health information (ePHI) and other forms of PII\n\nFor many applications, the Cloud Healthcare API can provide a cloud-based\nalternative to on-premises stacks implementing the following standards:\n\n- Digital Imaging and Communications in Medicine (DICOM)\n- Fast Healthcare Interoperability Resources (FHIR) DSTU2, STU3, and R4 standards\n- Health Level Seven Version 2.x (HL7v2)\n\nThe Cloud Healthcare API simplifies data integration with existing\nsystems and allows developers to focus on\ndifferentiating features, such as UX and intelligence.\n\nData model\n----------\n\nThe API consists of three modalities that implement individual industry-wide\nstandards:\n\n- Medical imaging data in the Digital Imaging and Communications in Medicine (DICOM) format\n- Clinical event messages in the Health Level Seven Version 2.x (HL7v2) format\n- Clinical resources in the Fast Healthcare Interoperability Resources (FHIR) format\n\nEach modality has different structural and processing characteristics, but\nthey are all backed by a standards-compliant data store that provides read,\nwrite, search, and other operations on the data.\n\nThe data stores corresponding to each modality reside in datasets, which are\ncontainers in your Google Cloud (Google Cloud) project that hold\nmodality-specific healthcare data.\n\nFor more information, see [Projects, datasets, and data stores](/healthcare-api/docs/concepts/projects-datasets-data-stores).\n\nFeatures of the Cloud Healthcare API\n------------------------------------\n\nThis section describes the features that make up the Cloud Healthcare API and the\nprimary purpose of each feature.\n\n### Standards conformance\n\nThe Cloud Healthcare API implements a REST API for multiple healthcare\nmodalities. For example:\n\n- The FHIR portion of the REST API conforms to the DSTU2, STU3, and R4 FHIR specifications.\n- The DICOM portion of the REST API conforms to DICOMweb, a web-based standard for exchanging medical images.\n\n### Compliance with privacy regulations\n\nThe Cloud Healthcare API is covered by Google Cloud's security,\nprivacy, and compliance assessments/certifications for industry standards,\nsuch as:\n\n- ISO 27001\n- ISO 27017\n- ISO 27018\n- PCI DSS\n\nThe Cloud Healthcare API is a covered service under the\nGoogle Cloud HIPAA BAA, which means that customers can use it\nwith electronic protected health information (ePHI), with\nappropriate configuration. The Cloud Healthcare API has been developed\naccording to Google's [security](/security/overview/whitepaper) and\n[privacy](/privacy) practices.\n\nGoogle Cloud provides detailed guidance regarding [compliance with HIPAA in the US,\nthe PIPEDA in Canada, and other global privacy standards](/security/compliance).\n\n### Data location control\n\nData location is a core component of the API. You can select the storage\nlocation for each dataset from a list of currently available locations that\ncorrespond to distinct geographic areas aligned with Google Cloud's\nregional structure. Data stores exist in the same region as their parent dataset.\n\nFor more information, see [Regions](/healthcare-api/docs/concepts/regions).\n\n### Security\n\nThe Cloud Healthcare API security model is based on Google's [Identity and\nAccess Management (IAM)](/iam) system. IAM's fine-grained permissions give you\ncomplete control over what can be done with healthcare data, and by whom.\nTo provide comprehensive threat detection and traffic management capabilities,\nthere are also implementations of open source proxies for the [Apigee\nAPI Management system](https://apigee.com/). You can use these implementations\nto securely expose sensitive ePHI with patient and provider applications.\n\n### Bulk import and export\n\nThe Cloud Healthcare API's DICOM and FHIR modalities support bulk import and export\nof data, making it easier to transfer data to and from [Cloud Storage](/storage).\n\nYou can also export FHIR resources and DICOM store metadata to [BigQuery](/bigquery).\nBigQuery lets you perform advanced data discovery and\nanalytics workloads on large datasets.\n\nFor more information, see [Importing and exporting DICOM data](/healthcare-api/docs/how-tos/dicom-import-export)\nand [Exporting DICOM metadata](/healthcare-api/docs/how-tos/dicom-export-bigquery).\n\n### Data de-identification\n\nThe Cloud Healthcare API supports de-identifying data at the dataset,\nFHIR store, and DICOM store level.\nDe-identification using the Cloud Healthcare API simplifies the process\nof redacting sensitive information for research and\nother purposes. For more information, see\n[Data de-identification](/healthcare-api/docs/concepts/de-identification).\n\n### Auditability\n\nYou can use [Cloud Logging](/logging) to audit administrative and data\naccess requests.\n\nFor more information, see [Access control](/healthcare-api/docs/access-control)\nand [Viewing Cloud Audit Logs](/healthcare-api/docs/how-tos/audit-logging).\n\n### High performance\n\nUsing Google Cloud's high-performance technology, the Cloud Healthcare API can scale to\nthousands of requests per second, even when accessing large volumes\nof data.\n\n### High availability\n\nAvailability for mission-critical scenarios is made possible through Google Cloud's\nrobust and highly redundant infrastructure.\n\n### Durability\n\nCloud Healthcare API is designed for 99.999999999% annual durability.\nDurability is\nachieved by storing data across multiple disks located in different power and\nnetwork failure domains."]]
