--- schema_version: "1" id: 492dbd28362ca3fd28865c7e7312694e48d6ccacf3775436a60b09450472dde9 title: Procedure collection: legacydeveloper version: current locale: en-us portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/life_sciences_dev_guide/map_fhir_Procedure.md canonical_url: https://developer.salesforce.com/docs/atlas.en-us.life_sciences_dev_guide.meta/life_sciences_dev_guide/map_fhir_Procedure.htm source_site: developer.salesforce.com content_type: documentation content_hash: e0f29500af94b7ddd2119005808aaac4c56345fc36d8c1c178ef579dd833543d description: The procedure FHIR resource maps to the PatientMedicalProcedure and PatientMedicalProcedureDetail objects in Salesforce. --- # Procedure The procedure FHIR resource maps to the PatientMedicalProcedure and PatientMedicalProcedureDetail objects in Salesforce. ## FHIR V4.0 - Clinical Data Model Mapping Here’s how the fields defined by FHIR for [Procedure](https://www.hl7.org/fhir/procedure.html) map to the fields in Salesforce.

Table 1. Procedure - Salesforce
Procedure Resource	Salesforce Field	Type	Salesforce Cardinality	Notes
`identifier`	`Identifier`	Object	0.M	The identifier information for a Procedure is represented as `Identifier` records that reference the PatientMedicalProcedure record using their `Identifier.ParentRecordId` field.
`instantiatesCanonical`	N/A	N/A	N/A	Not Supported
`instantiatesCanonical`	N/A	N/A	N/A	Not Supported
`basedOn`	`PatientMedicalProcedureDetail`	Object	0.M	The information about the service request that a procedure is based on is represented as `PatientMedicalProcedureDetail` records that reference the `PatientMedicalProcedure` record using their `PatientMedicalProcedureDetail.PatientMedicalProcedureId` field. The Salesforce implementation of `procedure.basedOn` doesn’t support references to care plans.
`basedOn`	`PatientMedicalProcedureDetail.DetailRecordId`	Lookup: `ClinicalServiceRequest`	0.1	For `procedure.basedOn` information, `PatientMedicalProcedureDetail.DetailRecordId` must reference a `ClinicalServiceRequest` record.
`basedOn`	`PatientMedicalProcedureDetail.DetailType`	Picklist Value: Based On	0.1	For `procedure.basedOn` information, `PatientMedicalProcedureDetail.DetailType` must use the value `Based On`.
`partOf`	`PatientMedicalProcedureDetail`	Object	0.M	The information about the procedure or observation that a procedure is a part of is represented as `PatientMedicalProcedureDetail` records that reference the `PatientMedicalProcedure` record using their `PatientMedicalProcedureDetail.PatientMedicalProcedureId` field. The Salesforce implementation of `procedure.partOf` doesn’t support references to medication administration.
`partOf`	`PatientMedicalProcedureDetail.DetailRecordId`	Polymorphic Lookup: `PatientMedicalProcedure`, `CareObservation`	0.1	For `procedure.partOf` information, `PatientMedicalProcedureDetail.DetailRecordId` must reference a either a `PatientMedicalProcedure` record or a `CareObservation`.
`partOf`	`PatientMedicalProcedureDetail.DetailType`	Picklist Value: Part Of	0.1	For `procedure.partOf` information, `PatientMedicalProcedureDetail.DetailType` must use the value `Part Of`.
`status`	`PatientMedicalProcedure.Status`	Picklist	0.1	While FHIR defines `procedure.status` as a code set bundle, the Salesforce implementation of `PatientMedicalProcedure.Status` is picklist.
`statusReason`	`PatientMedicalProcedure.StatusReasonCodeId`	Lookup: `CodeSetBundle`	0.1	N/A
`category`	`PatientMedicalProcedure.TypeId`	Lookup: `CodeSetBundle`	0.1	N/A
`code`	`PatientMedicalProcedure.CodeId`	Lookup: `CodeSetBundle`	0.1	N/A
`subject`	`PatientMedicalProcedure.PatientId`	MasterDetail: `Account`	1.1	The Salesforce implementation of `procedure.subject` doesn’t support references to groups.
`encounter`	`PatientMedicalProcedure.ClinicalEncounterId`	Lookup: `ClinicalEncounter`	0.1	N/A
`performed.performedDateTime`	`PatientMedicalProcedure.StartDate`	DateTime	0.1	`PatientMedicalProcedure.StartDate` is used for both `procedure.performed.performedDateTime` and `procedure.performed.performedPeriod`. For the latter, the field is used to represent the start date of the period.
`performed.performedPeriod`	`PatientMedicalProcedure.StartDate`	DateTime	0.1	Because Salesforce doesn’t support a native period data type, the `procedure.performed.performedPeriod` field is flattened into a set of start date and end date fields.
`performed.performedPeriod`	`PatientMedicalProcedure.EndDate`	DateTime	0.1	Because Salesforce doesn’t support a native period data type, the `procedure.performed.performedPeriod` field is flattened into a set of start date and end date fields.
`performed.performedString`	`PatientMedicalProcedure.DurationTimeString`	String	0.1	N/A
`performed.performedAge`	`PatientMedicalProcedure.PerformedAtAge`	Double	0.1	Because Salesforce doesn’t support a native age data type, the `procedure.performed.performedAge` FHIR resource is flattened into a set of age and unit fields.
`performed.performedAge`	`PatientMedicalProcedure.PerformedAtAgeUnitId`	Lookup: `UnitOfMeasure`	0.1	Because Salesforce doesn’t support a native age data type, the `procedure.performed.performedAge` FHIR resource is flattened into a set of age and unit fields.
`performed.performedRange`	`PatientMedicalProcedure.PerformedAtAgeLowerLimit`	Double	0.1	Because Salesforce doesn’t support a native range data type, the `procedure.performed.performedRange` FHIR resource is flattened into a set of lower limit, upper limit, and unit fields.
`performed.performedRange`	`PatientMedicalProcedure.PerformedAtAgeUpperLimit`	Double	0.1	Because Salesforce doesn’t support a native range data type, the `procedure.performed.performedRange` FHIR resource is flattened into a set of lower limit, upper limit, and unit fields.
`performed.performedRange`	`PatientMedicalProcedure.PerformedAgeRangeUnit`	Lookup: `UnitOfMeasure`	0.1	Because Salesforce doesn’t support a native range data type, the `procedure.performed.performedRange` FHIR resource is flattened into a set of lower limit, upper limit, and unit fields.
`recorder`	`PatientMedicalProcedure.RecordCreatorId`	Lookup: `Account`, `HealthcareProvider`	0.1	N/A
`asserter`	`PatientMedicalProcedure.AssertionSourceId`	Lookup: `Account`, `HealthcareProvider`	0.1	N/A
`performer`	`CarePerformer`	Object	0.M	The performer information for a Procedure is represented as `CarePerformer` records that reference the PatientMedicalProcedure record using their `CarePerformer.ParentRecordId` field.
`performer.function`	`CarePerformer.RoleId`	Polymorphic Lookup: `CodeSet`, `CodeSetBundle`	0.1	N/A
`performer.actor`	`CarePerformer.PersonId`	Polymorphic Lookup: `Account`, `HealthcareProvider`	0.1	The Salesforce implementation doesn’t support references to devices.
`performer.actor`onBehalfOf	`CarePerformer.AffiliatedOrganizationId`	Lookup: `Account`	0.1	0.1
`location`	`PatientMedicalProcedure.FacilityId`	Lookup: `Healthcare.Facility`	0.1	N/A
`reasonCode`	`PatientMedicalProcedure.ReasonCodeId`	Lookup: `CodeSetBundle`	0.1	While FHIR defines `procedure.reasonCode` as a zero-to-many resource, the Salesforce implementation is zero-to-one.
`reasonReference`	`PatientMedicalProcedure.ReasonReferenceId`	Polymorphic Lookup: `HealthCondition`, `CareObservation`, `PatientMedicalProcedure`, and `DiagnosticSummary`	0.1	While FHIR defines `procedure.reasonCode` as a zero-to-many resource, the Salesforce implementation is zero-to-one. The Salesforce implementation doesn’t support document reference records.
`bodySite`	`PatientMedicalProcedureDetail`	Object	0.M	The body site information of a procedure is represented as `PatientMedicalProcedureDetail` records that reference the `PatientMedicalProcedure` record using their `PatientMedicalProcedureDetail.PatientMedicalProcedureId` field.
`bodySite`	`PatientMedicalProcedureDetail.DetailCodeId`	Polymorphic Lookup: `CodeSet`, `CodeSetBundle`	0.1	For `procedure.bodySite` information, `PatientMedicalProcedureDetail.DetailCodeId` must reference a `CodeSet` or `CodeSetBundle` record.
`bodySite`	`PatientMedicalProcedureDetail.DetailType`	Picklist Value: Body Site	0.1	For `procedure.bodySite` information, `PatientMedicalProcedureDetail.DetailType` must use the value `Body Site`.
`outcome`	`PatientMedicalProcedure.Outcome`	Picklist	0.1	While FHIR defines `procedure.outcome` as a code, the Salesforce implementation of `PatientMedicalProcedure.Outcome` is a picklist.
`report`	`PatientMedicalProcedure.ReportId`	Lookup: `DiagnosticSummary`	0.1	While FHIR defines `procedure.report` as a zero-to-many resource, the Salesforce implementation is zero-to-one. The Salesforce implementation of `procedure.report` doesn’t support references to composition or document reference records.
`complication`	`PatientMedicalProcedureDetail`	Object	0.M	The complication information of a procedure is represented as `PatientMedicalProcedureDetail` records that reference the `PatientMedicalProcedure` record using their `PatientMedicalProcedureDetail.PatientMedicalProcedureId` field.
`complication`	`PatientMedicalProcedureDetail.DetailCodeId`	Polymorphic Lookup: `CodeSet`, `CodeSetBundle`	0.1	For `procedure.complication` information, `PatientMedicalProcedureDetail.DetailCodeId` must reference a `CodeSet` or `CodeSetBundle` record.
`complication`	`PatientMedicalProcedureDetail.DetailType`	Picklist Value: Complication	0.1	For `procedure.complication` information, `PatientMedicalProcedureDetail.DetailType` must use the value `Complication`.
`complicationDetail`	`PatientMedicalProcedureDetail`	Object	0.M	The complication detail information of a procedure is represented as `PatientMedicalProcedureDetail` records that reference the `PatientMedicalProcedure` record using their `PatientMedicalProcedureDetail.PatientMedicalProcedureId` field.
`complicationDetail`	`PatientMedicalProcedureDetail.DetailRecordId`	Lookup: `HealthCondition`	0.1	For `procedure.complicationDetail` information, `PatientMedicalProcedureDetail.DetailRecordId` must reference a `HealthCondition` record.
`complicationDetail`	`PatientMedicalProcedureDetail.DetailType`	Picklist Value: Complication Detail	0.1	For `procedure.complicationDetail` information, `PatientMedicalProcedureDetail.DetailType` must use the value `Complication Detail`.
`followUp`	`PatientMedicalProcedureDetail`	Object	0.M	The follow up information of a procedure is represented as `PatientMedicalProcedureDetail` records that reference the `PatientMedicalProcedure` record using their `PatientMedicalProcedureDetail.PatientMedicalProcedureId` field.
`followUp`	`PatientMedicalProcedureDetail.DetailCodeId`	Polymorphic Lookup: `CodeSet`, `CodeSetBundle`	0.1	For `procedure.followUp` information, `PatientMedicalProcedureDetail.DetailCodeId` must reference a `CodeSet` or `CodeSetBundle` record.
`followUp`	`PatientMedicalProcedureDetail.DetailType`	Picklist Value: Follow Up	0.1	For `procedure.complicationDetail` information, `PatientMedicalProcedureDetail.DetailType` must use the value `Follow Up`.
`Note`	`AuthorNote`	Object	0.M	Use the AuthorNote object to add notes to a procedure, and use the ParentRecordId field to reference the parent procedure the note belongs to.
`focalDevice`	`PatientMedicalProcedureDetail.DetailrecordId`	Lookup: CareRegisteredDevice	0.M	Use the `PatientMedicalProcedureDetail` child object to add multiple focalDevice values that reference the parent procedure record.
`usedReference`	`PatientMedicalProcedureDetail.DetailRecordId`	Lookup: CareRegisteredDevice	0.M	Use the `PatientMedicalProcedureDetail` child object to specify devices used in a procedure, and reference the parent procedure record.
`usedCode`	`PatientMedicalProcedureDetail.DetailCodeId`	N/A	0.M	Use the `PatientMedicalProcedureDetail` child object to specify codes for items used in a procedure, and reference the parent procedure record.

## Sample Record Diagram Here's a diagram that shows an example of how this resource is represented in Salesforce. ![A diagram that shows how a procedure for Charles' sinusectomy is represented in Salesforce.](https://developer.salesforce.com/docs/atlas.en-us.life_sciences_dev_guide.meta/life_sciences_dev_guide/dev_guides/healthcare_api/Mappings_FHIR/images/srd_hc_procedure.png) #### See Also - [CarePerformer](https://developer.salesforce.com/docs/atlas.en-us.life_sciences_dev_guide.meta/life_sciences_dev_guide/hc_r4_api_objects_CarePerformer.htm "Represents the person performing care in observations, procedure, and immunizations. This person may be a physician, the patient’s contact, or anyone who administered any sort of care to the patient in the context of the concerned care event. This object is available in API version 51.0 and later.") - [PatientMedicalProcedure](https://developer.salesforce.com/docs/atlas.en-us.life_sciences_dev_guide.meta/life_sciences_dev_guide/hc_r4_api_objects_patientmedicalprocedure.htm "Represents detailed information about a healthcare procedure the patient has undergone, is undergoing or will undergo. This object is available in API version 51.0 and later.") - [PatientMedicalProcedureDetail](https://developer.salesforce.com/docs/atlas.en-us.life_sciences_dev_guide.meta/life_sciences_dev_guide/hc_r4_api_objects_PatientMedicalProcedureDetail.htm "Associates records from different objects to a patient medical procedure record to add more information to the procedure record. This is a multi-object junction object. This object is available in API version 51.0 and later.")