Left: | Argonaut Procedure Profile (http://fhir.org/guides/argonaut/StructureDefinition/argo-procedure) |
Right: | US Core Procedure Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-procedure) |
Error | StructureDefinition.url | Values for url differ: 'http://fhir.org/guides/argonaut/StructureDefinition/argo-procedure' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-procedure' |
Information | StructureDefinition.name | Values for name differ: 'Argonaut Procedure Profile' vs 'USCoreProcedureProfile' |
Information | StructureDefinition.status | Values for status differ: 'draft' vs 'active' |
Information | StructureDefinition.date | Values for date differ: '2016-10-18T00:00:00+11:00' vs '2023-10-17' |
Information | StructureDefinition.publisher | Values for publisher differ: 'Argonaut Project' vs 'HL7 International / Cross-Group Projects' |
Information | StructureDefinition.jurisdiction | Added the item 'urn:iso:std:iso:3166#US' |
Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '1.0.2' vs '4.0.1' |
Information | StructureDefinition.short | Values for short differ: 'Argonaut Procedure Profile' vs 'An action that is being or was performed on a patient' |
Information | StructureDefinition.definition | Values for definition differ: 'An action that is or was performed on a patient. This can be a physical intervention like an operation, or less invasive like counseling or hypnotherapy.' vs '\-' |
Information | StructureDefinition.comment | Values for comment differ: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID.' vs 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.' |
Information | StructureDefinition.definition | Values for definition differ: 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.' vs 'The 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.' |
Information | StructureDefinition.definition | Values for definition differ: 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.' vs 'A 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.' |
Information | StructureDefinition.comment | Values for comment differ: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.' |
Information | StructureDefinition.comment | Values for comment differ: 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).' vs 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).' |
Information | StructureDefinition.definition | Values for definition differ: 'A human-readable narrative that contains a summary of the resource, and may 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.' vs 'A 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.' |
Information | StructureDefinition.comment | Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.' |
Information | StructureDefinition.comment | Values for comment differ: 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.' vs 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.' |
Information | StructureDefinition.short | Values for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations' |
Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource. In order 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.' vs '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.' |
Information | StructureDefinition.definition | Values for definition differ: '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. Usually modifier elements provide negation or qualification. In order 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.' vs '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).' |
Information | StructureDefinition.definition | Values for definition differ: 'This records identifiers associated with this procedure that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).' vs '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.' |
Information | StructureDefinition.requirements | Values for requirements differ: 'Need to allow connection to a wider workflow.' vs 'Allows identification of the procedure as it is known by various participating systems and in a way that remains consistent across servers.' |
Information | StructureDefinition.short | Values for short differ: 'in-progress | aborted | completed | entered-in-error' vs 'preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown' |
Information | StructureDefinition.definition | Values for definition differ: 'A code specifying the state of the procedure. Generally this will be in-progress or completed state.' vs 'A code specifying the state of the procedure. Generally, this will be the in-progress or completed state.' |
Error | Procedure.status | Unable to resolve left value set http://hl7.org/fhir/ValueSet/procedure-status at Procedure.status |
Information | StructureDefinition.short | Values for short differ: 'SNOMED-CT | ICD-10 | CPT-4' vs 'Identification of the procedure' |
Information | StructureDefinition.definition | Values for definition differ: 'Limited to 'real' people rather than equipment.' vs 'Limited to 'real' people rather than equipment.' |
Information | StructureDefinition.short | Values for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing' |
Information | StructureDefinition.definition | Values for definition differ: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.' |
Information | StructureDefinition.short | Values for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations' |
Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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.' |
Information | StructureDefinition.short | Values for short differ: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized' |
Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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).' |
Information | Procedure.performer.actor | Element minimum cardinalities differ: '0' vs '1' |
Information | StructureDefinition.short | Values for short differ: 'Date/Period the procedure was performed' vs 'When the procedure was performed' |
Information | StructureDefinition.definition | Values for definition differ: 'The date(time)/period over which 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.' vs 'Estimated 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.' |
Information | Procedure.performed[x] | Element minimum cardinalities differ: '1' vs '0' |
Information | StructureDefinition.short | Values for short differ: 'The encounter associated with the procedure' vs 'Encounter associated with the procedure' |
Information | StructureDefinition.definition | Values for definition differ: 'The encounter during which the procedure was performed.' vs 'The Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated.' |
Warning | Procedure.encounter | Elements differ in definition for mustSupport: 'false' vs 'true' |
Information | StructureDefinition.definition | Values for definition differ: 'The outcome of the procedure - did it resolve reasons for the procedure being performed?' vs 'The outcome of the procedure - did it resolve the reasons for the procedure being performed?' |
Information | StructureDefinition.definition | Values for definition differ: 'This could be a histology result, pathology report, surgical report, etc..' vs 'This could be a histology result, pathology report, surgical report, etc.' |
Information | StructureDefinition.definition | Values for definition differ: 'If the procedure required specific follow up - e.g. removal of sutures. The followup may be represented as a simple note, or could potentially be more complex in which case the CarePlan resource can be used.' vs '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.' |
Information | StructureDefinition.short | Values for short differ: 'Device changed in procedure' vs 'Manipulated, implanted, or removed device' |
Information | StructureDefinition.short | Values for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing' |
Information | StructureDefinition.definition | Values for definition differ: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.' |
Information | StructureDefinition.short | Values for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations' |
Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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.' |
Information | StructureDefinition.short | Values for short differ: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized' |
Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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).' |
Name | Value | Comments | |
---|---|---|---|
abstract | false | ||
baseDefinition | http://hl7.org/fhir/StructureDefinition/Procedure | ||
copyright | Used by permission of HL7 International, all rights reserved Creative Commons License |
| |
date | 2016-10-18T00:00:00+11:00 | 2023-10-17 |
|
description | The US Core Procedure Profile is based upon the core FHIR Procedure Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 'Procedures' requirements. This profile sets minimum expectations for the Procedure resource to record, search, and fetch procedures associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases. |
| |
experimental | false |
| |
fhirVersion | 1.0.2 | 4.0.1 |
|
jurisdiction | |||
jurisdiction[0] | urn:iso:std:iso:3166#US |
| |
kind | resource | ||
name | Argonaut Procedure Profile | USCoreProcedureProfile |
|
publisher | Argonaut Project | HL7 International / Cross-Group Projects |
|
purpose | |||
status | draft | active |
|
title | US Core Procedure Profile |
| |
type | Procedure | ||
url | http://fhir.org/guides/argonaut/StructureDefinition/argo-procedure | http://hl7.org/fhir/us/core/StructureDefinition/us-core-procedure |
|
version | 7.0.0-ballot |
|
Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Procedure | C | 0..* | Procedure | Argonaut Procedure Profile pro-1: Reason not performed is only permitted if notPerformed indicator is true | C | 0..* | Procedure | An action that is being or was performed on a patient us-core-7: Performed SHALL be present if the status is 'completed' or 'in-progress' | |||||
id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | |||||
meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | |||||
implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created | |||||
language | 0..1 | code | Language of the resource content Binding: ?? (required): A human language. | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| |||||||
text | 0..1 | Narrative | Text summary of the resource, for human interpretation | 0..1 | Narrative | Text summary of the resource, for human interpretation | |||||||
contained | 0..* | Resource | Contained, inline Resources | 0..* | Resource | Contained, inline Resources | |||||||
extension | 0..* | Extension | Additional Content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?! | 0..* | Extension | Extensions that cannot be ignored | |||||
identifier | Σ | 0..* | Identifier | External Identifiers for this procedure | Σ | 0..* | Identifier | External Identifiers for this procedure | |||||
subject | S | 1..1 | Reference(Argonaut Patient Profile) | Who the procedure was performed on | SΣ | 1..1 | Reference(US Core Patient Profile S | Group) | Who the procedure was performed on | |||||
status | ?!S | 1..1 | code | in-progress | aborted | completed | entered-in-error Binding: ?? (required) | ?!SΣC | 1..1 | code | preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown Binding: ?? (required) |
| ||||
category | Σ | 0..1 | CodeableConcept | Classification of the procedure Binding: ?? (example): A code that classifies a procedure for searching, sorting and display purposes. | Σ | 0..1 | CodeableConcept | Classification of the procedure Binding: ?? (example): A code that classifies a procedure for searching, sorting and display purposes. | |||||
code | S | 1..1 | CodeableConcept | SNOMED-CT | ICD-10 | CPT-4 Binding: ?? (extensible): Codes describing the Procedure Type
| SΣ | 1..1 | CodeableConcept | Identification of the procedure Binding: ?? (extensible): Codes describing the type of Procedure | |||||
notPerformed | ?! | 0..1 | boolean | True if procedure was not performed as scheduled |
| ||||||||
reasonNotPerformed | C | 0..* | CodeableConcept | Reason procedure was not performed Binding: ?? (example): A code that identifies the reason a procedure was not performed. |
| ||||||||
bodySite | Σ | 0..* | CodeableConcept | Target body sites Binding: ?? (example): Codes describing anatomical locations. May include laterality. | Σ | 0..* | CodeableConcept | Target body sites Binding: ?? (example): Codes describing anatomical locations. May include laterality. | |||||
reason[x] | Σ | 0..1 | CodeableConcept, Reference(Condition) | Reason procedure performed Binding: ?? (example): A code that identifies the reason a procedure is required. |
| ||||||||
performer | Σ | 0..* | BackboneElement | The people who performed the procedure | Σ | 0..* | BackboneElement | The people who performed the procedure | |||||
id | 0..1 | id | xml:id (or equivalent in JSON) | 0..1 | string | Unique id for inter-element referencing | |||||||
extension | 0..* | Extension | Additional Content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||
actor | Σ | 0..1 | Reference(Practitioner | Organization | Patient | RelatedPerson) | The reference to the practitioner | Σ | 1..1 | Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device) | The reference to the practitioner |
| ||||
role | Σ | 0..1 | CodeableConcept | The role the actor was in Binding: ?? (example): A code that identifies the role of a performer of the procedure. |
| ||||||||
function | Σ | 0..1 | CodeableConcept | Type of performance Binding: ?? (example): A code that identifies the role of a performer of the procedure. |
| ||||||||
onBehalfOf | 0..1 | Reference(Organization) | Organization the device or practitioner was acting for |
| |||||||||
performed[x] | S | 1..1 | dateTime, Period | Date/Period the procedure was performed | SΣC | 0..1 | dateTime S, Period, string, Age, Range | When the procedure was performed |
| ||||
encounter | Σ | 0..1 | Reference(Encounter) | The encounter associated with the procedure | SΣ | 0..1 | Reference(US Core Encounter Profile) | Encounter associated with the procedure |
| ||||
location | Σ | 0..1 | Reference(Location) | Where the procedure happened | Σ | 0..1 | Reference(Location) | Where the procedure happened | |||||
outcome | Σ | 0..1 | CodeableConcept | The result of procedure Binding: ?? (example): An outcome of a procedure - whether it was resolved or otherwise. | Σ | 0..1 | CodeableConcept | The result of procedure Binding: ?? (example): An outcome of a procedure - whether it was resolved or otherwise. | |||||
report | 0..* | Reference(DiagnosticReport) | Any report resulting from the procedure | 0..* | Reference(DiagnosticReport | DocumentReference | Composition) | Any report resulting from the procedure | |||||||
complication | 0..* | CodeableConcept | Complication following the procedure Binding: ?? (example): Codes describing complications that resulted from a procedure. | 0..* | CodeableConcept | Complication following the procedure Binding: ?? (example): Codes describing complications that resulted from a procedure. | |||||||
followUp | 0..* | CodeableConcept | Instructions for follow up Binding: ?? (example): Specific follow up required for a procedure e.g. removal of sutures. | 0..* | CodeableConcept | Instructions for follow up Binding: ?? (example): Specific follow up required for a procedure e.g. removal of sutures. | |||||||
request | 0..1 | Reference(CarePlan | DiagnosticOrder | ProcedureRequest | ReferralRequest) | A request for this procedure |
| |||||||||
notes | 0..* | Annotation | Additional information about the procedure |
| |||||||||
focalDevice | 0..* | BackboneElement | Device changed in procedure | 0..* | BackboneElement | Manipulated, implanted, or removed device | |||||||
id | 0..1 | id | xml:id (or equivalent in JSON) | 0..1 | string | Unique id for inter-element referencing | |||||||
extension | 0..* | Extension | Additional Content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||
action | 0..1 | CodeableConcept | Kind of change to device Binding: ?? (required): A kind of change that happened to the device during the procedure. | 0..1 | CodeableConcept | Kind of change to device Binding: ?? (preferred): A kind of change that happened to the device during the procedure. | |||||||
manipulated | 1..1 | Reference(Device) | Device that was changed | 1..1 | Reference(Device) | Device that was changed | |||||||
used | 0..* | Reference(Device | Medication | Substance) | Items used during procedure |
| |||||||||
instantiatesCanonical | Σ | 0..* | canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire) | Instantiates FHIR protocol or definition |
| ||||||||
instantiatesUri | Σ | 0..* | uri | Instantiates external protocol or definition |
| ||||||||
basedOn | Σ | 0..* | Reference(US Core CarePlan Profile | US Core ServiceRequest Profile) | 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: A request for this procedure |
| ||||||||
partOf | Σ | 0..* | Reference(Procedure | Observation | MedicationAdministration) | Part of referenced event |
| ||||||||
statusReason | Σ | 0..1 | CodeableConcept | Reason for current status Binding: ?? (example): A code that identifies the reason a procedure was not performed. |
| ||||||||
recorder | Σ | 0..1 | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) | Who recorded the procedure |
| ||||||||
asserter | Σ | 0..1 | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) | Person who asserts this procedure |
| ||||||||
reasonCode | Σ | 0..* | CodeableConcept | 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Coded reason procedure performed Binding: ?? (extensible) |
| ||||||||
reasonReference | Σ | 0..* | Reference(Condition | Observation | Procedure | DiagnosticReport | DocumentReference) | 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core Profile justifying the reason procedure performed |
| ||||||||
complicationDetail | 0..* | Reference(Condition) | A condition that is a result of the procedure |
| |||||||||
note | 0..* | Annotation | Additional information about the procedure |
| |||||||||
usedReference | 0..* | Reference(Device | Medication | Substance) | Items used during procedure |
| |||||||||
usedCode | 0..* | CodeableConcept | Coded items used during the procedure Binding: ?? (example): Codes describing items used during a procedure. |
| |||||||||
Documentation for this format |