procedures

Create Procedure

post
/organizations/{organizationId}/fhir/4/Procedure

An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy.

Request

Headers

content-type*stringapplication/json|application/json+fhirapplication/json
log-cdatastring
log-cdata-formatstringkv|jsonkv
AuthorizationstringBearer <token>

Params

organizationId*string|stringid|slug

Body

resourceType*This is a Procedure resource
ididThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
metaMetaThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
implicitRulesuriA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
languagecodeThe base language in which the resource is written.
textNarrativeA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
containedarray(ResourceList)These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
extensionarray(Extension)May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
modifierExtensionarray(Extension)May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
identifierarray(Identifier)Business identifiers assigned to this procedure by the performer or other systems which remain constant as the resource is updated and is propagated from server to server.
instantiatesCanonicalarray(canonical)The URL pointing to a FHIR-defined protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure.
instantiatesUriarray(uri)The URL pointing to an externally maintained protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure.
basedOnarray(Reference)A reference to a resource that contains details of the request for this procedure.
partOfarray(Reference)A larger event of which this particular procedure is a component or step.
statuscodeA code specifying the state of the procedure. Generally, this will be the in-progress or completed state.
statusReasonCodeableConceptCaptures the reason for the current state of the procedure.
categoryCodeableConceptA code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure").
codeCodeableConceptThe specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy").
subject*ReferenceThe person, animal or group on which the procedure was performed.
encounterReferenceThe Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated.
performedDateTimestringEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedPeriodPeriodEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedStringstringEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedAgeAgeEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedRangeRangeEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
recorderReferenceIndividual who recorded the record and takes responsibility for its content.
asserterReferenceIndividual who is making the procedure statement.
performerarray(Procedure_Performer)Limited to "real" people rather than equipment.
locationReferenceThe location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant.
reasonCodearray(CodeableConcept)The coded reason why the procedure was performed. This may be a coded entity of some type, or may simply be present as text.
reasonReferencearray(Reference)The justification of why the procedure was performed.
bodySitearray(CodeableConcept)Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion.
outcomeCodeableConceptThe outcome of the procedure - did it resolve the reasons for the procedure being performed?
reportarray(Reference)This could be a histology result, pathology report, surgical report, etc.
complicationarray(CodeableConcept)Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues.
complicationDetailarray(Reference)Any complications that occurred during the procedure, or in the immediate post-performance period.
followUparray(CodeableConcept)If the procedure required specific follow up - e.g. removal of sutures. The follow up may be represented as a simple note or could potentially be more complex, in which case the CarePlan resource can be used.
notearray(Annotation)Any other notes and comments about the procedure.
focalDevicearray(Procedure_FocalDevice)A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure.
usedReferencearray(Reference)Identifies medications, devices and any other substance used as part of the procedure.
usedCodearray(CodeableConcept)Identifies coded items that were used as part of the procedure.

Response

Patch Procedure

patch
/organizations/{organizationId}/fhir/4/Procedure/{resourceId}

An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy.

Request

Headers

content-type*stringapplication/json-patch+jsonapplication/json-patch+json
log-cdatastring
log-cdata-formatstringkv|jsonkv
AuthorizationstringBearer <token>

Params

organizationId*string|stringid|slug
resourceId*

Body

resourceType*This is a Procedure resource
ididThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
metaMetaThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
implicitRulesuriA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
languagecodeThe base language in which the resource is written.
textNarrativeA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
containedarray(ResourceList)These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
extensionarray(Extension)May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
modifierExtensionarray(Extension)May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
identifierarray(Identifier)Business identifiers assigned to this procedure by the performer or other systems which remain constant as the resource is updated and is propagated from server to server.
instantiatesCanonicalarray(canonical)The URL pointing to a FHIR-defined protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure.
instantiatesUriarray(uri)The URL pointing to an externally maintained protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure.
basedOnarray(Reference)A reference to a resource that contains details of the request for this procedure.
partOfarray(Reference)A larger event of which this particular procedure is a component or step.
statuscodeA code specifying the state of the procedure. Generally, this will be the in-progress or completed state.
statusReasonCodeableConceptCaptures the reason for the current state of the procedure.
categoryCodeableConceptA code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure").
codeCodeableConceptThe specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy").
subject*ReferenceThe person, animal or group on which the procedure was performed.
encounterReferenceThe Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated.
performedDateTimestringEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedPeriodPeriodEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedStringstringEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedAgeAgeEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedRangeRangeEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
recorderReferenceIndividual who recorded the record and takes responsibility for its content.
asserterReferenceIndividual who is making the procedure statement.
performerarray(Procedure_Performer)Limited to "real" people rather than equipment.
locationReferenceThe location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant.
reasonCodearray(CodeableConcept)The coded reason why the procedure was performed. This may be a coded entity of some type, or may simply be present as text.
reasonReferencearray(Reference)The justification of why the procedure was performed.
bodySitearray(CodeableConcept)Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion.
outcomeCodeableConceptThe outcome of the procedure - did it resolve the reasons for the procedure being performed?
reportarray(Reference)This could be a histology result, pathology report, surgical report, etc.
complicationarray(CodeableConcept)Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues.
complicationDetailarray(Reference)Any complications that occurred during the procedure, or in the immediate post-performance period.
followUparray(CodeableConcept)If the procedure required specific follow up - e.g. removal of sutures. The follow up may be represented as a simple note or could potentially be more complex, in which case the CarePlan resource can be used.
notearray(Annotation)Any other notes and comments about the procedure.
focalDevicearray(Procedure_FocalDevice)A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure.
usedReferencearray(Reference)Identifies medications, devices and any other substance used as part of the procedure.
usedCodearray(CodeableConcept)Identifies coded items that were used as part of the procedure.

Response

Read Procedure

get
/organizations/{organizationId}/fhir/4/Procedure/{resourceId}

Request

Headers

content-type*stringapplication/json|application/json+fhirapplication/json
log-cdatastring
log-cdata-formatstringkv|jsonkv
AuthorizationstringBearer <token>

Params

organizationId*string|stringid|slug
resourceId*

Response

Read History Procedure

get
/organizations/{organizationId}/fhir/4/Procedure/{resourceId}/_history

Request

Headers

content-type*stringapplication/json|application/json+fhirapplication/json
log-cdatastring
log-cdata-formatstringkv|jsonkv
AuthorizationstringBearer <token>

Query params

_countstring
_sincestring

Params

organizationId*string|stringid|slug
resourceId*

Response

Read Version Procedure

get
/organizations/{organizationId}/fhir/4/Procedure/{resourceId}/_history/{versionId}

Request

Headers

content-type*stringapplication/json|application/json+fhirapplication/json
log-cdatastring
log-cdata-formatstringkv|jsonkv
AuthorizationstringBearer <token>

Params

organizationId*string|stringid|slug
resourceId*
versionId*

Response

Remove Procedure

delete
/organizations/{organizationId}/fhir/4/Procedure/{resourceId}

Request

Headers

content-type*stringapplication/json|application/json+fhirapplication/json
log-cdatastring
log-cdata-formatstringkv|jsonkv
AuthorizationstringBearer <token>

Params

organizationId*string|stringid|slug
resourceId*

Response

Search Get Procedure

get
/organizations/{organizationId}/fhir/4/Procedure

Request

Headers

content-type*stringapplication/json|application/json+fhirapplication/json
log-cdatastring
log-cdata-formatstringkv|jsonkv
AuthorizationstringBearer <token>

Query params

_idstring
_languagestring
based-onstring
categorystring
codestring
datestring
encounterstring
identifierstring
instantiates-canonicalstring
instantiates-uristring
locationstring
part-ofstring
patientstring
performerstring
reason-codestring
reason-referencestring
statusstring
subjectstring

Params

organizationId*string|stringid|slug

Response

Search History Procedure

get
/organizations/{organizationId}/fhir/4/Procedure/_history

Request

Headers

content-type*stringapplication/json|application/json+fhirapplication/json
log-cdatastring
log-cdata-formatstringkv|jsonkv
AuthorizationstringBearer <token>

Query params

_countstring
_sincestring

Params

organizationId*string|stringid|slug

Response

Search Post Procedure

post
/organizations/{organizationId}/fhir/4/Procedure/_search

An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy.

Request

Headers

content-type*stringapplication/json|application/x-www-form-urlencodedapplication/json
log-cdatastring
log-cdata-formatstringkv|jsonkv
AuthorizationstringBearer <token>

Query params

_idstring
_languagestring
based-onstring
categorystring
codestring
datestring
encounterstring
identifierstring
instantiates-canonicalstring
instantiates-uristring
locationstring
part-ofstring
patientstring
performerstring
reason-codestring
reason-referencestring
statusstring
subjectstring

Params

organizationId*string|stringid|slug

Body

resourceType*This is a Procedure resource
ididThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
metaMetaThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
implicitRulesuriA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
languagecodeThe base language in which the resource is written.
textNarrativeA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
containedarray(ResourceList)These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
extensionarray(Extension)May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
modifierExtensionarray(Extension)May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
identifierarray(Identifier)Business identifiers assigned to this procedure by the performer or other systems which remain constant as the resource is updated and is propagated from server to server.
instantiatesCanonicalarray(canonical)The URL pointing to a FHIR-defined protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure.
instantiatesUriarray(uri)The URL pointing to an externally maintained protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure.
basedOnarray(Reference)A reference to a resource that contains details of the request for this procedure.
partOfarray(Reference)A larger event of which this particular procedure is a component or step.
statuscodeA code specifying the state of the procedure. Generally, this will be the in-progress or completed state.
statusReasonCodeableConceptCaptures the reason for the current state of the procedure.
categoryCodeableConceptA code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure").
codeCodeableConceptThe specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy").
subject*ReferenceThe person, animal or group on which the procedure was performed.
encounterReferenceThe Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated.
performedDateTimestringEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedPeriodPeriodEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedStringstringEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedAgeAgeEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedRangeRangeEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
recorderReferenceIndividual who recorded the record and takes responsibility for its content.
asserterReferenceIndividual who is making the procedure statement.
performerarray(Procedure_Performer)Limited to "real" people rather than equipment.
locationReferenceThe location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant.
reasonCodearray(CodeableConcept)The coded reason why the procedure was performed. This may be a coded entity of some type, or may simply be present as text.
reasonReferencearray(Reference)The justification of why the procedure was performed.
bodySitearray(CodeableConcept)Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion.
outcomeCodeableConceptThe outcome of the procedure - did it resolve the reasons for the procedure being performed?
reportarray(Reference)This could be a histology result, pathology report, surgical report, etc.
complicationarray(CodeableConcept)Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues.
complicationDetailarray(Reference)Any complications that occurred during the procedure, or in the immediate post-performance period.
followUparray(CodeableConcept)If the procedure required specific follow up - e.g. removal of sutures. The follow up may be represented as a simple note or could potentially be more complex, in which case the CarePlan resource can be used.
notearray(Annotation)Any other notes and comments about the procedure.
focalDevicearray(Procedure_FocalDevice)A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure.
usedReferencearray(Reference)Identifies medications, devices and any other substance used as part of the procedure.
usedCodearray(CodeableConcept)Identifies coded items that were used as part of the procedure.

Response

Update Procedure

put
/organizations/{organizationId}/fhir/4/Procedure/{resourceId}

An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy.

Request

Headers

content-type*stringapplication/json|application/json+fhirapplication/json
log-cdatastring
log-cdata-formatstringkv|jsonkv
AuthorizationstringBearer <token>

Params

organizationId*string|stringid|slug
resourceId*

Body

resourceType*This is a Procedure resource
ididThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
metaMetaThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
implicitRulesuriA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
languagecodeThe base language in which the resource is written.
textNarrativeA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
containedarray(ResourceList)These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
extensionarray(Extension)May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
modifierExtensionarray(Extension)May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
identifierarray(Identifier)Business identifiers assigned to this procedure by the performer or other systems which remain constant as the resource is updated and is propagated from server to server.
instantiatesCanonicalarray(canonical)The URL pointing to a FHIR-defined protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure.
instantiatesUriarray(uri)The URL pointing to an externally maintained protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure.
basedOnarray(Reference)A reference to a resource that contains details of the request for this procedure.
partOfarray(Reference)A larger event of which this particular procedure is a component or step.
statuscodeA code specifying the state of the procedure. Generally, this will be the in-progress or completed state.
statusReasonCodeableConceptCaptures the reason for the current state of the procedure.
categoryCodeableConceptA code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure").
codeCodeableConceptThe specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy").
subject*ReferenceThe person, animal or group on which the procedure was performed.
encounterReferenceThe Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated.
performedDateTimestringEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedPeriodPeriodEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedStringstringEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedAgeAgeEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
performedRangeRangeEstimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
recorderReferenceIndividual who recorded the record and takes responsibility for its content.
asserterReferenceIndividual who is making the procedure statement.
performerarray(Procedure_Performer)Limited to "real" people rather than equipment.
locationReferenceThe location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant.
reasonCodearray(CodeableConcept)The coded reason why the procedure was performed. This may be a coded entity of some type, or may simply be present as text.
reasonReferencearray(Reference)The justification of why the procedure was performed.
bodySitearray(CodeableConcept)Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion.
outcomeCodeableConceptThe outcome of the procedure - did it resolve the reasons for the procedure being performed?
reportarray(Reference)This could be a histology result, pathology report, surgical report, etc.
complicationarray(CodeableConcept)Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues.
complicationDetailarray(Reference)Any complications that occurred during the procedure, or in the immediate post-performance period.
followUparray(CodeableConcept)If the procedure required specific follow up - e.g. removal of sutures. The follow up may be represented as a simple note or could potentially be more complex, in which case the CarePlan resource can be used.
notearray(Annotation)Any other notes and comments about the procedure.
focalDevicearray(Procedure_FocalDevice)A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure.
usedReferencearray(Reference)Identifies medications, devices and any other substance used as part of the procedure.
usedCodearray(CodeableConcept)Identifies coded items that were used as part of the procedure.

Response