Generated Narrative: StructureDefinition ext-R5-Account.procedure Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.3.0) The list of procedures relevant to this account #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Closed by value:url #xD; extension:sequence 0..1 Extension Ranking of the procedure (for each type) #xD; url 1..1 uri "sequence" #xD; value[x] 0..1 positiveInt Ranking of the procedure (for each type) #xD; extension:code 1..1 Extension The procedure relevant to the account #xD; url 1..1 uri "code" #xD; value[x] 0..1 CodeableReference() The procedure relevant to the account Binding: R5_procedure_code_for_R4B (0.0.1-snapshot-2) (example) #xD; extension:dateOfService 0..1 Extension Date of the procedure (when coded procedure) #xD; url 1..1 uri "dateOfService" #xD; value[x] 0..1 dateTime Date of the procedure (when coded procedure) #xD; extension:type 0..* Extension How this procedure value should be used in charging the account #xD; url 1..1 uri "type" #xD; value[x] 0..1 CodeableConcept How this procedure value should be used in charging the account #xD; extension:packageCode 0..* Extension Package Code specific for billing #xD; url 1..1 uri "packageCode" #xD; value[x] 0..1 CodeableConcept Package Code specific for billing #xD; extension:device 0..* Extension Any devices that were associated with the procedure #xD; url 1..1 uri "device" #xD; value[x] 0..1 Reference() Any devices that were associated with the procedure #xD; url 1..1 uri "http://hl7.org/fhir/5.0/StructureDefinition/extension-Account.procedure" #xD; Documentation for this format
Cross-version Extension for R5.Account.procedure for use in FHIR R4B
This cross-version extension represents Account.procedure from http://hl7.org/fhir/StructureDefinition/Account|5.0.0 for use in FHIR R4B.
The list of procedures relevant to this account
When using an account for billing a specific Encounter the set of procedures that are relevant for billing are stored here on the account where they are able to be sequenced appropriately prior to processing to produce claim(s).
`Account.procedure` has no related element in R4B:Account
All FHIR elements must have a @value or children unless an empty Parameters resource
hasValue() or (children().count() > id.count()) or $this is Parameters
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
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
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Ranking of the procedure (for each type)
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.
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Date of the procedure (when coded procedure)
Date of the procedure when using a coded procedure. If using a reference to a procedure, then the date on the procedure should be used.
How this procedure value should be used in charging the account
The package code can be used to group procedures that may be priced or delivered as a single product. Such as DRGs.
Any devices that were associated with the procedure
Any devices that were associated with the procedure relevant to the account.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4B/extensibility.html) for a list).