Da Vinci Unsolicited Notifications Implementation Guide (Release 0.2.0 STU1 Ballot)

This page is part of the Da Vinci Unsolicited Notifications (v0.2.0: STU 1 Ballot 1) based on FHIR R4. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

StructureDefinition-admit-discharge-notification-encounter

The Da Vinci Admit Notification Encounter Profile is based on the US Core Encounter Profile and and constrains the resources referenced by the Encounter.Subject,Encounter.Location, and Encounter.participant.individual to be found in the same message Bundle. In addition, the Location reference is constrained to the US Core Location Profile

Mandatory and Must Support Data Elements

The following data-elements are mandatory (i.e data MUST be present) or must be supported if the data is present in the sending system (Must Support definition). They are presented below in a simple human-readable explanation. Profile specific guidance and examples are provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.

Each Encounter must support:

  1. A reference(s) to US Core Encounter Location(s) which will be bundled in the message.

Examples

The following examples of this profile are freestanding resource instances. Note that these are technically invalid since the profile is defined to references other resources within the same Da Vinci Notification Message Bundle. A complete list of examples including bundle examples can be found on the Examples page.

Formal Views of Profile Content

Description of Profiles, Differentials, and Snapshots.

The official URL for this profile is: http://hl7.org/fhir/us/davinci-alerts/StructureDefinition/admit-discharge-notification-encounter

Published on Tue Nov 12 08:00:00 UTC 2019 as active by the Health eData Inc.

This profile builds on USCoreEncounterProfile

Encounter

Summary of the Mandatory Requirements

  1. A Patient Reference in Encounter.subject

Summary of the Must Support Requirements

  1. One or more Participants in Encounter.participant
    • which should have an Individual Reference value in Encounter.participant.individual
  2. One or more Locations in Encounter.location
    • which must have a Location Reference value in Encounter.location.location
NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter I0..*USCoreEncounterProfileAn interaction during which services are provided to the patient
... id Σ0..1stringLogical id of this artifact
... meta ΣI0..1MetaMetadata about the resource
... implicitRules ?!ΣI0..1uriA set of rules under which this content was created
... language I0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred)
Max Binding: AllLanguages
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension I0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!I0..*ExtensionExtensions that cannot be ignored
... identifier SΣI0..*IdentifierIdentifier(s) by which this encounter is known
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... use ?!ΣI0..1codeusual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required)
.... type ΣI0..1CodeableConceptDescription of identifier
Binding: Identifier Type Codes (extensible)
.... system SΣI1..1uriThe namespace for the identifier value
Example General: http://www.acme.com/identifiers/patient
.... value SΣI1..1stringThe value that is unique
Example General: 123456
.... period ΣI0..1PeriodTime period when id is/was valid for use
.... assigner ΣI0..1Reference(Organization)Organization that issued id (may be just text)
... status ?!SΣI1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
Binding: EncounterStatus (required)
... statusHistory I0..*BackboneElementList of past encounter statuses
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... status I1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
Binding: EncounterStatus (required)
.... period I1..1PeriodThe time that the episode was in the specified status
... class SΣI1..1CodingClassification of patient encounter
Binding: V3 Value SetActEncounterCode (extensible)
... classHistory I0..*BackboneElementList of past encounter classes
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... class I1..1Codinginpatient | outpatient | ambulatory | emergency +
Binding: V3 Value SetActEncounterCode (extensible)
.... period I1..1PeriodThe time that the episode was in the specified class
... type SΣI1..*CodeableConceptSpecific type of encounter
Binding: US Core Encounter Type (extensible)
... serviceType ΣI0..1CodeableConceptSpecific type of service
Binding: ServiceType (example)
... priority I0..1CodeableConceptIndicates the urgency of the encounter
Binding: v3 Code System ActPriority (example)
... subject SΣI1..1Reference(US Core Patient Profile) {b}The patient or group present at the encounter
... episodeOfCare ΣI0..*Reference(EpisodeOfCare)Episode(s) of care that this encounter should be recorded against
... basedOn I0..*Reference(ServiceRequest)The ServiceRequest that initiated this encounter
... participant SΣI0..*BackboneElementList of participants involved in the encounter
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... type SΣI0..*CodeableConceptRole of participant in encounter
Binding: ParticipantType (extensible)
.... period SI0..1PeriodPeriod of time during the encounter that the participant participated
.... individual SΣI0..1Reference(US Core Practitioner Profile) {b}Persons involved in the encounter other than the patient
... appointment ΣI0..*Reference(Appointment)The appointment that scheduled this encounter
... period SI0..1PeriodThe start and end time of the encounter
... length I0..1DurationQuantity of time the encounter lasted (less time absent)
... reasonCode SΣI0..*CodeableConceptCoded reason the encounter takes place
Binding: EncounterReasonCodes (preferred)
... reasonReference ΣI0..*Reference(Condition | Procedure | Observation | ImmunizationRecommendation)Reason the encounter takes place (reference)
... diagnosis ΣI0..*BackboneElementThe list of diagnosis relevant to this encounter
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... condition ΣI1..1Reference(Condition | Procedure)The diagnosis or procedure relevant to the encounter
.... use I0..1CodeableConceptRole that this diagnosis has within the encounter (e.g. admission, billing, discharge …)
Binding: DiagnosisRole (preferred)
.... rank I0..1positiveIntRanking of the diagnosis (for each role type)
... account I0..*Reference(Account)The set of accounts that may be used for billing for this Encounter
... hospitalization SI0..1BackboneElementDetails about the admission to a healthcare service
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... preAdmissionIdentifier I0..1IdentifierPre-admission identifier
.... origin I0..1Reference(Location | Organization)The location/organization from which the patient came before admission
.... admitSource I0..1CodeableConceptFrom where patient was admitted (physician referral, transfer)
Binding: AdmitSource (preferred)
.... reAdmission I0..1CodeableConceptThe type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
Binding: v2 RE-ADMISSION INDICATOR (example)
.... dietPreference I0..*CodeableConceptDiet preferences reported by the patient
Binding: Diet (example)
.... specialCourtesy I0..*CodeableConceptSpecial courtesies (VIP, board member)
Binding: SpecialCourtesy (preferred)
.... specialArrangement I0..*CodeableConceptWheelchair, translator, stretcher, etc.
Binding: SpecialArrangements (preferred)
.... destination I0..1Reference(Location | Organization)Location/organization to which the patient is discharged
.... dischargeDisposition SI0..1CodeableConceptCategory or kind of location after discharge
Binding: DischargeDisposition (example)
... location SI0..*BackboneElementList of locations where the patient has been
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... location SI1..1Reference(US Core Location Profile) {b}Location the encounter takes place
.... status I0..1codeplanned | active | reserved | completed
Binding: EncounterLocationStatus (required)
.... physicalType I0..1CodeableConceptThe physical type of the location (usually the level in the location hierachy - bed room ward etc.)
Binding: LocationType (example)
.... period I0..1PeriodTime period during which the patient was present at the location
... serviceProvider I0..1Reference(Organization)The organization (facility) responsible for this encounter
... partOf I0..1Reference(Encounter)Another Encounter this encounter is part of

doco Documentation for this format

Encounter

Summary of the Mandatory Requirements

  1. A Patient Reference in Encounter.subject

Summary of the Must Support Requirements

  1. One or more Participants in Encounter.participant
    • which should have an Individual Reference value in Encounter.participant.individual
  2. One or more Locations in Encounter.location
    • which must have a Location Reference value in Encounter.location.location

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter I0..*USCoreEncounterProfileAn interaction during which services are provided to the patient
... id Σ0..1stringLogical id of this artifact
... meta ΣI0..1MetaMetadata about the resource
... implicitRules ?!ΣI0..1uriA set of rules under which this content was created
... language I0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred)
Max Binding: AllLanguages
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension I0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!I0..*ExtensionExtensions that cannot be ignored
... identifier SΣI0..*IdentifierIdentifier(s) by which this encounter is known
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... use ?!ΣI0..1codeusual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required)
.... type ΣI0..1CodeableConceptDescription of identifier
Binding: Identifier Type Codes (extensible)
.... system SΣI1..1uriThe namespace for the identifier value
Example General: http://www.acme.com/identifiers/patient
.... value SΣI1..1stringThe value that is unique
Example General: 123456
.... period ΣI0..1PeriodTime period when id is/was valid for use
.... assigner ΣI0..1Reference(Organization)Organization that issued id (may be just text)
... status ?!SΣI1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
Binding: EncounterStatus (required)
... statusHistory I0..*BackboneElementList of past encounter statuses
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... status I1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
Binding: EncounterStatus (required)
.... period I1..1PeriodThe time that the episode was in the specified status
... class SΣI1..1CodingClassification of patient encounter
Binding: V3 Value SetActEncounterCode (extensible)
... classHistory I0..*BackboneElementList of past encounter classes
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... class I1..1Codinginpatient | outpatient | ambulatory | emergency +
Binding: V3 Value SetActEncounterCode (extensible)
.... period I1..1PeriodThe time that the episode was in the specified class
... type SΣI1..*CodeableConceptSpecific type of encounter
Binding: US Core Encounter Type (extensible)
... serviceType ΣI0..1CodeableConceptSpecific type of service
Binding: ServiceType (example)
... priority I0..1CodeableConceptIndicates the urgency of the encounter
Binding: v3 Code System ActPriority (example)
... subject SΣI1..1Reference(US Core Patient Profile) {b}The patient or group present at the encounter
... episodeOfCare ΣI0..*Reference(EpisodeOfCare)Episode(s) of care that this encounter should be recorded against
... basedOn I0..*Reference(ServiceRequest)The ServiceRequest that initiated this encounter
... participant SΣI0..*BackboneElementList of participants involved in the encounter
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... type SΣI0..*CodeableConceptRole of participant in encounter
Binding: ParticipantType (extensible)
.... period SI0..1PeriodPeriod of time during the encounter that the participant participated
.... individual SΣI0..1Reference(US Core Practitioner Profile) {b}Persons involved in the encounter other than the patient
... appointment ΣI0..*Reference(Appointment)The appointment that scheduled this encounter
... period SI0..1PeriodThe start and end time of the encounter
... length I0..1DurationQuantity of time the encounter lasted (less time absent)
... reasonCode SΣI0..*CodeableConceptCoded reason the encounter takes place
Binding: EncounterReasonCodes (preferred)
... reasonReference ΣI0..*Reference(Condition | Procedure | Observation | ImmunizationRecommendation)Reason the encounter takes place (reference)
... diagnosis ΣI0..*BackboneElementThe list of diagnosis relevant to this encounter
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... condition ΣI1..1Reference(Condition | Procedure)The diagnosis or procedure relevant to the encounter
.... use I0..1CodeableConceptRole that this diagnosis has within the encounter (e.g. admission, billing, discharge …)
Binding: DiagnosisRole (preferred)
.... rank I0..1positiveIntRanking of the diagnosis (for each role type)
... account I0..*Reference(Account)The set of accounts that may be used for billing for this Encounter
... hospitalization SI0..1BackboneElementDetails about the admission to a healthcare service
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... preAdmissionIdentifier I0..1IdentifierPre-admission identifier
.... origin I0..1Reference(Location | Organization)The location/organization from which the patient came before admission
.... admitSource I0..1CodeableConceptFrom where patient was admitted (physician referral, transfer)
Binding: AdmitSource (preferred)
.... reAdmission I0..1CodeableConceptThe type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
Binding: v2 RE-ADMISSION INDICATOR (example)
.... dietPreference I0..*CodeableConceptDiet preferences reported by the patient
Binding: Diet (example)
.... specialCourtesy I0..*CodeableConceptSpecial courtesies (VIP, board member)
Binding: SpecialCourtesy (preferred)
.... specialArrangement I0..*CodeableConceptWheelchair, translator, stretcher, etc.
Binding: SpecialArrangements (preferred)
.... destination I0..1Reference(Location | Organization)Location/organization to which the patient is discharged
.... dischargeDisposition SI0..1CodeableConceptCategory or kind of location after discharge
Binding: DischargeDisposition (example)
... location SI0..*BackboneElementList of locations where the patient has been
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... location SI1..1Reference(US Core Location Profile) {b}Location the encounter takes place
.... status I0..1codeplanned | active | reserved | completed
Binding: EncounterLocationStatus (required)
.... physicalType I0..1CodeableConceptThe physical type of the location (usually the level in the location hierachy - bed room ward etc.)
Binding: LocationType (example)
.... period I0..1PeriodTime period during which the patient was present at the location
... serviceProvider I0..1Reference(Organization)The organization (facility) responsible for this encounter
... partOf I0..1Reference(Encounter)Another Encounter this encounter is part of

doco Documentation for this format

See the Conformance requirements for a complete list of supported RESTful interactions for this IG.