이 페이지에서는 Google Cloud프로젝트와 Cloud Healthcare API 데이터 세트 및 데이터 저장소 간의 관계를 설명합니다.
프로젝트
모든 Cloud Healthcare API는 Google Cloud프로젝트의 컨텍스트 내에서 사용됩니다. 프로젝트는 모든 Google Cloud 리소스를 구성합니다.
프로젝트는 사용자 집합, API 집합, 그리고 이러한 API에 대한 청구, 인증, 모니터링 설정으로 구성됩니다. 예를 들어 모든 Cloud Healthcare API 데이터 및 리소스는 여기에 액세스할 수 있는 사용자 권한과 함께 프로젝트에 상주합니다. 프로젝트를 하나만 갖거나 여러 프로젝트를 만들 수 있으며 이를 사용하여 Google Cloud
Cloud Healthcare API 데이터를 포함한 리소스를 논리적 그룹으로 구성할 수 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-05(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:"]]
