PLMsimPatientSummaryProcedure
| PLMsimPatientSummaryProcedure (Procedure) | C | Procedure | There are no (further) constraints on this element Element idProcedureShort description An action that is being or was performed on a patient DefinitionAn 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.
| |||
| id | Σ | 0..1 | id | There are no (further) constraints on this element Element idProcedure.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idProcedure.metaShort description Metadata about the resource DefinitionThe 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idProcedure.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idProcedure.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language. Binding extensions
The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| text | C | 0..1 | Narrative | There are no (further) constraints on this element Element idProcedure.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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. 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 in formation is added later. The cardinality or value of this element may be affected by these constraints: ele-1, dom-1 Constraints
| ||
| contained | 0..* | Resource | There are no (further) constraints on this element Element idProcedure.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idProcedure.extensionShort description Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idProcedure.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idProcedure.identifierShort description External Identifiers for this procedure DefinitionThis 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). Need to allow connection to a wider workflow. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| definition | Σ C | 0..0 | Reference(PlanDefinition | ActivityDefinition | HealthcareService) | There are no (further) constraints on this element Element idProcedure.definitionShort description Instantiates protocol or definition DefinitionA protocol, guideline, orderset or other definition that was adhered to in whole or in part by this procedure. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(PlanDefinition | ActivityDefinition | HealthcareService) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| basedOn | Σ C | 0..0 | Reference(CarePlan | http://hl7.org/fhir/StructureDefinition/ProcedureRequest | http://hl7.org/fhir/StructureDefinition/ReferralRequest) | There are no (further) constraints on this element Element idProcedure.basedOnShort description A request for this procedure Alternate namesfulfills DefinitionA reference to a resource that contains details of the request for this procedure. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(CarePlan | http://hl7.org/fhir/StructureDefinition/ProcedureRequest | http://hl7.org/fhir/StructureDefinition/ReferralRequest) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| partOf | Σ C | 0..0 | Reference(Procedure) | There are no (further) constraints on this element Element idProcedure.partOfShort description Part of referenced event Alternate namescontainer DefinitionA larger event of which this particular procedure is a component or step. The MedicationAdministration has a partOf reference to Procedure, but this is not a circular reference. For a surgical procedure, the anesthesia related medicationAdministration is part of the procedure. For an IV medication administration, the procedure to insert the IV port is part of the medication administration. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| status | S Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idProcedure.statusShort description preparation | in-progress | suspended | aborted | completed | entered-in-error | unknown DefinitionA code specifying the state of the procedure. Generally this will be in-progress or completed state. The unknown code is not to be used to convey other statuses. The unknown code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. A code specifying the state of the procedure. ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| notDone | Σ ?! | 0..0 | boolean | There are no (further) constraints on this element Element idProcedure.notDoneShort description True if procedure was not performed as scheduled DefinitionSet this to true if the record is saying that the procedure was NOT performed. If true, it means the procedure did not occur as described. Typically it would be accompanied by attributes describing the type of activity. It might also be accompanied by body site information or time information (i.e. no procedure was done to the left arm or no procedure was done in this 2-year period). Specifying additional information such as performer, outcome, etc. is generally inappropriate. For example, it's not that useful to say "There was no appendectomy done at 12:03pm June 6th by Dr. Smith with a successful outcome" as it implies that there could have been an appendectomy done at any other time, by any other clinician or with any other outcome. This element is labeled as a modifier because it indicates that a procedure didn't happen. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
falseMappings
| ||
| notDoneReason | Σ C | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idProcedure.notDoneReasonShort description Reason procedure was not performed DefinitionA code indicating why the procedure was not performed. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A code that identifies the reason a procedure was not performed. ProcedureNotPerformedReason(SNOMED-CT) (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, pro-1 Constraints
| ||
| category | Σ | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idProcedure.categoryShort description Classification of the procedure DefinitionA code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure"). Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A code that classifies a procedure for searching, sorting and display purposes. ProcedureCategoryCodes(SNOMEDCT) (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| code | S Σ | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idProcedure.codeShort description Identification of the procedure Alternate namestype DefinitionThe specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy"). 0..1 to account for primarily narrative only resources. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Unordered, Open, by coding.system(Value) BindingA code to identify a specific procedure . http://hl7.org/fhir/uv/ips/ValueSet/procedures-uv-ips (preferred) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| absentOrUnknownProcedure | S Σ | 0..1 | http://hl7.org/fhir/uv/ips/StructureDefinition/codeableconcept-uv-ipsBinding | There are no (further) constraints on this element Element idProcedure.code:absentOrUnknownProcedureShort description Identification of the procedure Alternate namestype DefinitionThe specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy"). 0..1 to account for primarily narrative only resources. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. http://hl7.org/fhir/uv/ips/StructureDefinition/codeableconcept-uv-ips BindingA code to identify absent or unknown procedures http://hl7.org/fhir/uv/ips/ValueSet/absent-or-unknown-procedures-uv-ips (required) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| procedureCode | S Σ | 0..1 | http://hl7.org/fhir/uv/ips/StructureDefinition/codeableconcept-uv-ipsBinding | There are no (further) constraints on this element Element idProcedure.code:procedureCodeShort description Identification of the procedure Alternate namestype DefinitionThe specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy"). 0..1 to account for primarily narrative only resources. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. http://hl7.org/fhir/uv/ips/StructureDefinition/codeableconcept-uv-ips BindingA code to identify a specific procedure . http://hl7.org/fhir/uv/ips/ValueSet/procedures-uv-ips (preferred) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| subject | S Σ C | 1..1 | Reference(Patient) | There are no (further) constraints on this element Element idProcedure.subjectShort description Who the procedure was performed on Alternate namespatient DefinitionThe person on which the procedure was performed. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idProcedure.subject.idShort description xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idProcedure.subject.extensionShort description Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| reference | Σ C | 0..1 | string | There are no (further) constraints on this element Element idProcedure.subject.referenceShort description Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. The cardinality or value of this element may be affected by these constraints: ele-1, ref-1 Constraints
| ||
| identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idProcedure.subject.identifierShort description Logical reference, when literal reference is not known DefinitionAn identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| display | Σ | 0..1 | string | There are no (further) constraints on this element Element idProcedure.subject.displayShort description Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| context | Σ C | 0..0 | Reference(Encounter | EpisodeOfCare) | There are no (further) constraints on this element Element idProcedure.contextShort description Encounter or episode associated with the procedure Alternate namesencounter DefinitionThe encounter during which the procedure was performed. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Encounter | EpisodeOfCare) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| performed[x] | S Σ | 1..1 | There are no (further) constraints on this element Element idProcedure.performed[x]Short description Date/Period the procedure was performed DefinitionThe 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| performedDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
| performedPeriod | Period | There are no (further) constraints on this element Data type | ||||
| performer | Σ | 0..0 | BackboneElement | There are no (further) constraints on this element Element idProcedure.performerShort description The people who performed the procedure DefinitionLimited to 'real' people rather than equipment. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| location | Σ C | 0..0 | Reference(Location) | There are no (further) constraints on this element Element idProcedure.locationShort description Where the procedure happened DefinitionThe location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant. Ties a procedure to where the records are likely kept. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. TRILLIUM II IMPLEMENTATION COMMENTS: We propose to encode it with SNOMED CT. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| reasonCode | Σ | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idProcedure.reasonCodeShort description Coded reason procedure performed DefinitionThe coded reason why the procedure was performed. This may be coded entity of some type, or may simply be present as text. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A code that identifies the reason a procedure is required. ProcedureReasonCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| reasonReference | Σ C | 0..0 | Reference(Condition | Observation) | There are no (further) constraints on this element Element idProcedure.reasonReferenceShort description Condition that is the reason the procedure performed DefinitionThe condition that is the reason why the procedure was performed. e.g. endoscopy for dilatation and biopsy, combination diagnosis and therapeutic. Reference(Condition | Observation) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| bodySite | S Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idProcedure.bodySiteShort description Target body sites DefinitionDetailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Codes describing anatomical locations. May include laterality. http://hl7.org/fhir/uv/ips/ValueSet/target-site-uv-ips (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| outcome | Σ | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idProcedure.outcomeShort description The result of procedure DefinitionThe outcome of the procedure - did it resolve reasons for the procedure being performed? If outcome contains narrative text only, it can be captured using the CodeableConcept.text. An outcome of a procedure - whether it was resolved or otherwise. ProcedureOutcomeCodes(SNOMEDCT) (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| report | C | 0..0 | Reference(DiagnosticReport) | There are no (further) constraints on this element Element idProcedure.reportShort description Any report resulting from the procedure DefinitionThis could be a histology result, pathology report, surgical report, etc.. There could potentially be multiple reports - e.g. if this was a procedure which took multiple biopsies resulting in a number of anatomical pathology reports. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| complication | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idProcedure.complicationShort description Complication following the procedure DefinitionAny 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. If complications are only expressed by the narrative text, they can be captured using the CodeableConcept.text. Codes describing complications that resulted from a procedure. Condition/Problem/DiagnosisCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| complicationDetail | C | 0..0 | Reference(Condition) | There are no (further) constraints on this element Element idProcedure.complicationDetailShort description A condition that is a result of the procedure DefinitionAny complications that occurred during the procedure, or in the immediate post-performance period. This is used to document a condition that is a result of the procedure, not the condition that was the reason for the procedure. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| followUp | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idProcedure.followUpShort description Instructions for follow up DefinitionIf 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. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Specific follow up required for a procedure e.g. removal of sutures. ProcedureFollowUpCodes(SNOMEDCT) (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| note | 0..0 | Annotation | There are no (further) constraints on this element Element idProcedure.noteShort description Additional information about the procedure DefinitionAny other notes about the procedure. E.g. the operative notes. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| focalDevice | 0..0 | BackboneElement | There are no (further) constraints on this element Element idProcedure.focalDeviceShort description Device changed in procedure DefinitionA 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| usedReference | C | 0..0 | Reference(Device | Medication | Substance) | There are no (further) constraints on this element Element idProcedure.usedReferenceShort description Items used during procedure DefinitionIdentifies medications, devices and any other substance used as part of the procedure. Used for tracking contamination, etc. For devices actually implanted or removed, use Procedure.device. Reference(Device | Medication | Substance) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| usedCode | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idProcedure.usedCodeShort description Coded items used during the procedure DefinitionIdentifies coded items that were used as part of the procedure. For devices actually implanted or removed, use Procedure.device. Codes describing items used during a procedure ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
|