This page describes the relationship between Google Cloud Platform (GCP) projects and Cloud Healthcare API datasets and data stores.
All Cloud Healthcare API usage occurs within the context of a GCP project. A project organizes all your GCP resources. A project consists of a set of users; a set of APIs; and billing, authentication, and monitoring settings for those APIs. So, for example, all of your Cloud Healthcare API data and resources, along with user permissions for accessing them, reside in a project. You can have one project, or you can create multiple projects and use them to organize your GCP resources, including your Cloud Healthcare API data, into logical groups.
Each project that you use to develop Cloud Healthcare API solutions must have the Cloud Healthcare API enabled.
To learn more about GCP projects in general, see Projects in the Google Cloud Platform Overview.
Datasets and data stores
A dataset is a container in your GCP project that holds modality-specific healthcare data. Datasets contain other data stores, such as FHIR stores, DICOM stores, and HL7v2 stores, which in turn hold their own types of healthcare data.
A single dataset can contain one or many data stores, and those stores can all service the same modality or different modalities as application needs dictate. Using multiple stores in the same dataset might be appropriate in various situations, such as:
- If an application processes different types of data, such as a DICOM store used for CT scans and a FHIR store for patient data related to the CT scans.
- To separate data according to its source hospital, clinic, department, and so forth.
An application can access as many datasets or stores as its requirements dictate with no performance penalty. You can design your overall dataset and store architecture to meet your goals for locality, partitioning, access control, and so forth.
The following diagram shows a single GCP project containing two datasets. Each dataset contains multiple data stores, and each data store contains healthcare data: