The date a billed service was delivered, carried on the Invoice line item that bills it.
Invoice.date is the billing date, not the date of service, and R4 Invoice has no element for the
latter. A claim may bill several services on different dates, one per line.
The date a billed service was delivered, carried on the Invoice line item that bills it.
Invoice.date is the billing date, not the date of service, and R4 Invoice has no element for the
latter. A claim may bill several services on different dates, one per line.
MIGRATION. The billing conversion writes this today at
https://apps.health/InvoiceLineItem/service-date. Write the canonical declared here; when reading,
expect both addresses until stored invoices are migrated.
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.
Comments
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.
Comments
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.