url | ResearchStudy.UniformResourceIdentifier | URL | 0.1 | N/A |
identifier | ResearchStudy.Identifier | Object | 0.M | The identifier information for a research study is represented as Identifier records that reference the ResearchStudy record using their Identifier.ParentRecordId field. |
name | ResearchStudy.Name | Text | 1.1 | While FHIR defines researchStudy.name as a zero-to-one resource, the Salesforce implementation of ResearchStudy.Name is one-to-one. |
title | ResearchStudy.Title | Long Text Area | 0.1 | While FHIR defines researchStudy.type as a text, the Salesforce implementation of ResearchStudy.Title is a long text area. |
date | ResearchStudy.SourceSystemModified | Date/Time | 1.1 | N/A |
status | ResearchStudy.PublicationStatus | Picklist | 1.1 | N/A |
primaryPurposeType | ResearchStudy.IntentType | Picklist | 0.1 | N/A |
phase | ResearchStudy.Phase | Picklist | 0.1 | N/A |
| studyDesign | CareProgramDetail.DetailRecord | Lookup: CodeSet, CodeSetBundle, OmniProcess, CarePlanTemplate | 1.M | While FHIR defines researchStudy.studyDesign as a zero-to-many resource, the Salesforce implementation of CareProgramDetail.DetailRecord is one-to-many. |
| focus | CareProgramDetail.DetailRecord | Lookup: CodeSet, CodeSetBundle, OmniProcess, CarePlanTemplate | 1.M | While FHIR defines researchStudy.focus as a zero-to-many resource, the Salesforce implementation of CareProgramDetail.DetailRecord is one-to-many. |
| condition | CareProgramDetail.DetailRecord | Lookup: CodeSet, CodeSetBundle, OmniProcess, CarePlanTemplate | 1.M | While FHIR defines researchStudy.condition as a zero-to-many resource, the Salesforce implementation of CareProgramDetail.DetailRecord is one-to-many. |
| keyword | CareProgramDetail.DetailRecord | Lookup: CodeSet, CodeSetBundle, OmniProcess, CarePlanTemplate | 1.M | While FHIR defines researchStudy.keyword as a zero-to-many resource, the Salesforce implementation of CareProgramDetail.DetailRecord is one-to-many. |
| region | CareProgramDetail.DetailRecord | Lookup: CodeSet, CodeSetBundle, OmniProcess, CarePlanTemplate | | While FHIR defines researchStudy.region as a zero-to-many resource, the Salesforce implementation of CareProgramDetail.DetailRecord is one-to-many. |
description.Summary | ResearchStudy.Summary | Long Text Area | 0.1 | N/A |
description | ResearchStudy.Description | Long Text Area | 0.1 | N/A |
period | ResearchStudy.StartDate | Date/Time | 0.1 | Since Salesforce doesn’t natively support the period data type, researchStudy.Period is flattened into a set of start date and end date fields. The start date field is also used as the equivalent of researchStudy.periodDateTime. |
period | ResearchStudy.EndDate | Date/Time | 0.1 | Since Salesforce doesn’t natively support the period data type, researchStudy.Period is flattened into a set of start date and end date fields. The start date field is also used as the equivalent of researchStudy.periodDateTime. |
| site | CareProgramSite.HealthCareFacility | Lookup: HealthCareFacility | 0.M | N/A |
| classifier | CareProgramSite.DetailRecord | Lookup: CodeSet, CodeSetBundle, OmniProcess, CarePlanTemplate | 1.M | While FHIR defines researchStudy.classifier as a zero-to-many resource, the Salesforce implementation of CareProgramSite.DetailRecord is one-to-many. |
| associatedParty.name | CareProgramTeamMember.Member | Polymorphic Lookup | 0.1 | While FHIR defines researchStudy.associatedParty.name as a text, the Salesforce implementation of CareProgramTeamMember.Member is a polymorphic lookup. |
| associatedParty.role | CareProgramTeamMemberRolePeriod.Role | DynamicEnum | 1.1 | N/A |
associatedParty.period | CareProgramTeamMemberRolePeriod.EffectiveStartDate | Date/Time | 0.1 | Since Salesforce doesn’t natively support the period data type, researchStudy.associatedParty.period is flattened into a set of start date and end date fields. The start date field is also used as the equivalent of researchStudy.periodDateTime. |
associatedParty.period | CareProgramTeamMemberRolePeriod.EffectiveEndDate | Date/Time | 0.1 | Since Salesforce doesn’t natively support the period data type, researchStudy.associatedParty.period is flattened into a set of start date and end date fields. The start date field is also used as the equivalent of researchStudy.periodDateTime. |
| associatedParty.classifier | CareProgramTeamMember.Category | Multi-Select | 0.M | While FHIR defines researchStudy.associatedParty.name as a CodeSetBundle, the Salesforce implementation of CareProgramTeamMember.Category is Multi-Select. |
| progressStatus.state | CareProgramStatusPeriod.Status | DynamicEnum | 1.M | While FHIR defines researchStudy.state as a zero-to-many resource, the Salesforce implementation of CareProgramDetail.DetailRecord is one-to-many. |
| progressStatus.actual | CareProgramStatusPeriod.AreDatesTentative | Boolean | 0.1 | N/A |
| progressStatus.period | CareProgramStatusPeriod.EffectiveStartDateTime | Date/Time | 0.1 | Since Salesforce doesn’t natively support the period data type, researchStudy.progressStatus.period is flattened into effective start date time field. |
| progressStatus.period | CareProgramStatusPeriod.EffectiveEndDateTime | Date/Time | 0.1 | Since Salesforce doesn’t natively support the period data type, researchStudy.progressStatus.period is flattened into an effective end date time field. |
whyStopped | ResearchStudy.DiscontinuationReason | Picklist | 0.1 | While FHIR defines researchStudy.whyStopped as a code set bundle, the Salesforce implementation of ResearchStudy.DiscontinuationReason is a picklist. |
| recruitment.targetnumber | CareProgram.TargetEnrolleeCount | Number | 0.1 | N/A |
| recruitment.actualnumber | CareProgram.CurrentEnrolleeCount | Number | 0.1 | N/A |
recruitment.eligibility | ResearchStudy.InclusionExclusionCriteria | Rich Text Area | 0.1 | N/A |
| comparisonGroup.name | ResearchStudyComparisonGroup.Name | Text | 1.1 | N/A |
| comparisonGroup.type | ResearchStudyComparisonGroup.TypeCode | Lookup: CodeSet | 1.1 | While FHIR defines researchStudy.comparisonGroup.type as a zero-to-one resource, the Salesforce implementation of CareProgramDetail.TypeCode is one-to-one. |
| comparisonGroup.description | ResearchStudyComparisonGroup.Description | Text | 0.1 | N/A |
| objective.name | CareProgramGoal.Name | Long Text Area | 1.1 | While FHIR defines researchStudy.objective.name as a zero-to-one resource, the Salesforce implementation of CareProgramGoal.Name is one-to-one. |
| objective.type | CareProgramGoal.Type | Picklist | 0.1 | N/A |
| objective.description | CareProgramGoal.Description | Long Text Area | 0.1 | N/A |
| result | DiagnosticSummary.BasedOn | Lookup: Medication Statement, Clinical Service Request | 0.1 | N/A |
j