Stay organized with collections
Save and categorize content based on your preferences.
This page describes the relationship between Google Cloud
projects and Cloud Healthcare API datasets and data stores.
Projects
All Cloud Healthcare API usage occurs within the context of a Google Cloud
project. A project organizes all your Google Cloud 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 Google Cloud
resources, including your Cloud Healthcare API data, into logical groups.
To learn more about Google Cloud projects in general,
see Projects in the Google Cloud Overview.
Datasets and data stores
A dataset is a container in your Google Cloud 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 Google Cloud project containing
two datasets. Each dataset contains multiple data stores, and each data store
contains healthcare data:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eAll Cloud Healthcare API activity occurs within a Google Cloud project, which organizes resources, users, APIs, billing, authentication, and monitoring settings.\u003c/p\u003e\n"],["\u003cp\u003eDatasets, which are containers within a Google Cloud project, hold healthcare data in modality-specific data stores like FHIR, DICOM, and HL7v2.\u003c/p\u003e\n"],["\u003cp\u003eA dataset can contain multiple data stores, which are designed to manage various data types or organize data by source, and can also cater to diverse application requirements.\u003c/p\u003e\n"],["\u003cp\u003eEach project must have the Cloud Healthcare API enabled in order to use it's features.\u003c/p\u003e\n"]]],[],null,["# Projects, datasets, and data stores\n\nThis page describes the relationship between Google Cloud\nprojects and Cloud Healthcare API datasets and data stores.\n\nProjects\n--------\n\nAll Cloud Healthcare API usage occurs within the context of a Google Cloud\nproject. A project organizes all your Google Cloud resources.\nA project consists of a set of users; a set of APIs; and billing,\nauthentication, and monitoring settings for those APIs. So, for example,\nall of your Cloud Healthcare API data and resources, along with user\npermissions for accessing them, reside in a project. You can have one project,\nor you can create multiple projects and use them to organize your Google Cloud\nresources, including your Cloud Healthcare API data, into logical groups.\n\nEach project that you use to develop Cloud Healthcare API solutions must\nhave the [Cloud Healthcare API enabled](/apis/docs/enable-disable-apis).\n\nTo learn more about Google Cloud projects in general,\nsee [Projects](/docs/overview#projects) in the Google Cloud Overview.\n\nDatasets and data stores\n------------------------\n\nA dataset is a container in your Google Cloud project that holds\nmodality-specific healthcare data. Datasets contain other data stores, such\nas FHIR stores, DICOM stores, and HL7v2 stores, which in turn hold their own\ntypes of healthcare data.\n\nA single dataset can contain one or many data stores, and those stores can\nall service the same modality or different modalities as application needs\ndictate. Using multiple stores in the same dataset might be appropriate in\nvarious situations, such as:\n\n- 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.\n- To separate data according to its source hospital, clinic, department, and so forth.\n\nAn application can access as many datasets or stores as its requirements\ndictate with no performance penalty. You can design your overall dataset\nand store architecture to meet your goals for locality, partitioning,\naccess control, and so forth.\n\nThe following diagram shows a single Google Cloud project containing\ntwo datasets. Each dataset contains multiple data stores, and each data store\ncontains healthcare data:"]]
