Generated Narrative: StructureDefinition be-model-procedure Name Flags Card. Type Description & Constraints be-model-procedure 0..* Base BeProcedure Model #xD; identifier 1..* Identifier Unique identifier for the procedure #xD; recordedDate 1..1 dateTime Date of the last modification/recording of the procedure #xD; performedDate[x] 1..1 Date or period when the procedure was actually performed #xD; performedDateDateTime dateTime #xD; performedDatePeriod Period #xD; patient 1..1 Reference() The patient that is the subject of the procedure. #xD; recorder 1..1 Reference() Person, organization or device that recorded the procedure. #xD; performer 0..1 Reference(Practitioner | PractitionerRole | Organization) Person who performed the procedure. #xD; request 0..* Reference() CarePlan and/or Referral Prescription that is at the origin of the procedure. For example: a physiotherapy session performed on prescription from the general practitioner #xD; partOf 0..* Reference() Part of the event being referenced: procedure, observation (symptoms) or problem (disease). For example: Blood draw (procedure) is part of the diagnostic observation (Observation) #xD; category 0..* CodeableConcept Type or nature of the procedure. For example: surgical, psychiatric or chiropractic procedures #xD; focalDevice 0..* CodeableReference() Implanted or manipulated device #xD; usedDevice 0..* Reference() Devices or materials used temporarily during the procedure. For example: surgical robot, intraoperative imaging, neuronavigation. This also includes substances such as gels. Standard small instruments such as scalpels and syringes are not recorded #xD; status 1..1 code Procedure status (not-done, stopped, completed, entered-in-error). Note: 'not-done' is out of scope as it implies planning. Business Rule: 'completed' by default #xD; code 1..1 CodeableConcept Identification of the procedure (SNOMED-CT Procedure concept) #xD; reason 0..* BackboneElement Reason why the procedure is performed. For example: amputation after an accident, broken leg #xD; reasonCode 0..1 CodeableConcept Coded reason why the procedure is performed #xD; reasonReference 0..1 Reference() Reference to the condition, observation or procedure that is the reason #xD; bodySite 0..1 BeModelBodySite The site on the patient's body where the procedure was performed #xD; surgicalApproach 0..* CodeableConcept Indicates by which anatomical route or according to which technique the procedure was performed. For example: laparoscopic, endoscopic, percutaneous #xD; location 0..1 Reference() Reference to the location where the procedure was performed. Example: Healthcare provider's office, Patient's home, Hospital, Outpatient, other #xD; outcome 0..1 CodeableConcept Result of the procedure execution. Example: Partial success, Success, Unsuccessful #xD; report 0..* Reference() Any report resulting from the procedure. Currently this is expected to be an attached document (pdf, URL, jpg, etc.). In the future possibly reference to a DiagnosticReport or other data object #xD; note 0..* Annotation Additional information about the procedure #xD; Documentation for this format
Date of the last modification/recording of the procedure
Date or period when the procedure was actually performed
Date or period when the procedure was actually performed. For example: the date of an operation or the period during which a treatment was carried out
The patient that is the subject of the procedure.
The patient that is the subject of the procedure. This includes the patient's Social Security Identification Number (NISS), generally corresponding to the national registry number. In some cases, another unique identification code may be authorized, such as the BIS number
Person, organization or device that recorded the procedure.
Person, organization or device that recorded the procedure. For a healthcare provider, this is the Social Security Identification Number (NISS). For an organization, the Crossroads Bank for Social Security (BCSS) number is used. For a medical device, use the unique device identification number
Person who performed the procedure. For a healthcare provider, this is the Social Security Identification Number (NISS). For an organization, the BCSS number is used. For a medical device, use the unique device identification number
CarePlan and/or Referral Prescription that is at the origin of the procedure. For example: a physiotherapy session performed on prescription from the general practitioner
Part of the event being referenced: procedure, observation (symptoms) or problem (disease). For example: Blood draw (procedure) is part of the diagnostic observation (Observation)
Type or nature of the procedure. For example: surgical, psychiatric or chiropractic procedures
Devices or materials used temporarily during the procedure. For example: surgical robot, intraoperative imaging, neuronavigation. This also includes substances such as gels. Standard small instruments such as scalpels and syringes are not recorded
Procedure status (not-done, stopped, completed, entered-in-error). Note: 'not-done' is out of scope as it implies planning. Business Rule: 'completed' by default
Identification of the procedure (SNOMED-CT Procedure concept)
Reason why the procedure is performed. For example: amputation after an accident, broken leg
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
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.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Extensions that cannot be ignored even if unrecognized
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).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Coded reason why the procedure is performed
Reference to the condition, observation or procedure that is the reason
The site on the patient's body where the procedure was performed
Indicates by which anatomical route or according to which technique the procedure was performed. For example: laparoscopic, endoscopic, percutaneous
Reference to the location where the procedure was performed. Example: Healthcare provider's office, Patient's home, Hospital, Outpatient, other
Result of the procedure execution. Example: Partial success, Success, Unsuccessful
Any report resulting from the procedure. Currently this is expected to be an attached document (pdf, URL, jpg, etc.). In the future possibly reference to a DiagnosticReport or other data object
Additional information about the procedure