Generated Narrative: StructureDefinition profile-EpisodeOfCare Name Flags Card. Type Description & Constraints EpisodeOfCare 0..* EpisodeOfCare An association of a Patient with an Organization and Healthcare Provider(s) for a period of time that the Organization assumes some level of responsibility #xD; referralRequest #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:referralRequest 0..* ?gen-e1? [CanonicalType[http://hl7.org/fhir/StructureDefinition/alternate-reference]] R4: referralRequest additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; careManager #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:careManager 0..1 ?gen-e1? [CanonicalType[http://hl7.org/fhir/StructureDefinition/alternate-reference]] R4: Care manager/care coordinator for the patient additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; Documentation for this format
Cross-version Profile for R4.EpisodeOfCare for use in FHIR STU3
This cross-version profile allows R4 EpisodeOfCare content to be represented via FHIR STU3 EpisodeOfCare resources.
An association of a Patient with an Organization and Healthcare Provider(s) for a period of time that the Organization assumes some level of responsibility
An association between a patient and an organization / healthcare provider(s) during which time encounters may occur. The managing organization assumes a level of responsibility for the patient during this time.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL NOT contain any narrative
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource
contained.where(('#'+id in %resource.descendants().reference).not()).empty()
not(exists(for $id in f:contained/*/@id return $id[not(ancestor::f:contained/parent::*/descendant::f:reference/@value=concat('#', $id))]))
The 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 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.
A set of rules under which this content was created
A 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 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).
Text summary of the resource, for human interpretation
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.
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.
These 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.
Additional Content defined by implementations
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.
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.
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.
Business Identifier(s) relevant for this EpisodeOfCare
The EpisodeOfCare may be known by different identifiers for different contexts of use, such as when an external agency is tracking the Episode for funding purposes.
planned | waitlist | active | onhold | finished | cancelled | entered-in-error
planned | waitlist | active | onhold | finished | cancelled.
This element is labeled as a modifier because the status contains codes that mark the episode as not currently valid.
Past list of status codes (the current status may be included to cover the start date of the status)
The history of statuses that the EpisodeOfCare has been through (without requiring processing the history of the resource).
All FHIR elements must have a @value or children
hasValue() | (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.
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.
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.
Duration the EpisodeOfCare was in the specified status
The period during this EpisodeOfCare that the specific status applied.
Type/class - e.g. specialist referral, disease management
A classification of the type of episode of care; e.g. specialist referral, disease management, type of funded care.
The type can be very important in processing as this could be used in determining if the EpisodeOfCare is relevant to specific government reporting, or other types of classifications.
The list of diagnosis relevant to this episode of care
The list of diagnosis relevant to this episode of care.
Conditions/problems/diagnoses this episode of care is for
A list of conditions/problems/diagnoses that this episode of care is intended to be providing care for.
Role that this diagnosis has within the episode of care (e.g. admission, billing, discharge …)
Role that this diagnosis has within the episode of care (e.g. admission, billing, discharge …).
The type of diagnosis this condition represents
Ranking of the diagnosis (for each role type)
Ranking of the diagnosis (for each role type).
The patient who is the focus of this episode of care
The patient who is the focus of this episode of care.
The organization that has assumed the specific responsibilities for the specified duration.
Interval during responsibility is assumed
The interval during which the managing organization assumes the defined responsibility.
Referral Request(s) that are fulfilled by this EpisodeOfCare, incoming referrals.
Extensions are always sliced by (at least) url
R4: `EpisodeOfCare.referralRequest` additional types from child elements (display, identifier, reference, type)
Element `EpisodeOfCare.referralRequest` is mapped to FHIR STU3 element `EpisodeOfCare.referralRequest` as `SourceIsBroaderThanTarget`. The mappings for `EpisodeOfCare.referralRequest` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4 element `EpisodeOfCare.referralRequest` with unmapped reference targets: ServiceRequest.
Literal reference, Relative, internal or absolute URL
A 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.
Logical reference, when literal reference is not known
An 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.
Plain 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.
Care manager/care co-ordinator for the patient
The practitioner that is the care manager/care co-ordinator for this patient.
R4: Care manager/care coordinator for the patient additional types
R4: `EpisodeOfCare.careManager` additional types from child elements (display, identifier, reference, type)
Element `EpisodeOfCare.careManager` is mapped to FHIR STU3 element `EpisodeOfCare.careManager` as `SourceIsBroaderThanTarget`. The mappings for `EpisodeOfCare.careManager` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4 element `EpisodeOfCare.careManager` with unmapped reference targets: PractitionerRole.
Other practitioners facilitating this episode of care
The list of practitioners that may be facilitating this episode of care for specific purposes.
The set of accounts that may be used for billing for this EpisodeOfCare
The set of accounts that may be used for billing for this EpisodeOfCare.
The billing system may choose to allocate billable items associated with the EpisodeOfCare to different referenced Accounts based on internal business rules.