Da Vinci Unsolicited Notifications Implementation Guide CI Build

Da Vinci Unsolicited Notifications, published by HL7 International - Infrastructure and Messaging Work Group. This is not an authorized publication; it is the continuous build for version 0.2.1). This version is based on the current content of https://github.com/HL7/davinci-alerts/ and changes regularly. See the Directory of published versions

StructureDefinition-admit-discharge-notification-condition

The Da Vinci Admit Notification Condition Profile is based on the US Core Condition Profile and adds the mandatory Condition.encounter element which references the US Core Encounter Profile in the same message Bundle.

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 Condition must have:

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

Additional Profile specific implementation guidance:

Note that for the admission/discharge scenario, Condition.encounter is a “reverse link” to the Encounter resource and cannot be traversed from the MessageHeader within the Message Bundle.

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-condition

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

This profile builds on USCoreCondition


Condition

Summary of the Mandatory Requirements

  1. An Encounter Reference in Condition.encounter

Summary of Constraints

  1. Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item
  2. If condition is abated, then clinicalStatus must be either inactive, resolved, or remission
  3. Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error
  4. A code in Condition.category SHOULD be from US Core Condition Category Codes value set.
NameFlagsCard.TypeDescription & Constraintsdoco
.. Condition I0..*USCoreConditionDetailed information about conditions, problems or diagnoses
... 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 ΣI0..*IdentifierExternal Ids for this condition
... clinicalStatus ?!SΣI0..1CodeableConceptactive | recurrence | relapse | inactive | remission | resolved
Binding: ConditionClinicalStatusCodes (required)
... verificationStatus ?!SΣI0..1CodeableConceptunconfirmed | provisional | differential | confirmed | refuted | entered-in-error
Binding: ConditionVerificationStatus (required)
... category SI1..*CodeableConceptproblem-list-item | encounter-diagnosis | health-concern
Binding: US Core Condition Category Codes (extensible)
... severity I0..1CodeableConceptSubjective severity of condition
Binding: Condition/DiagnosisSeverity (preferred)
... code SΣI1..1CodeableConceptIdentification of the condition, problem or diagnosis
Binding: US Core Condition Code (extensible)
... bodySite ΣI0..*CodeableConceptAnatomical location, if relevant
Binding: SNOMEDCTBodyStructures (example)
... subject SΣI1..1Reference(US Core Patient Profile)Who has the condition?
... encounter SΣI1..1Reference(US Core Encounter Profile) {b}Encounter created as part of
... onset[x] ΣI0..1Estimated or actual date, date-time, or age
.... onsetDateTimedateTime
.... onsetAgeAge
.... onsetPeriodPeriod
.... onsetRangeRange
.... onsetStringstring
... abatement[x] I0..1When in resolution/remission
.... abatementDateTimedateTime
.... abatementAgeAge
.... abatementPeriodPeriod
.... abatementRangeRange
.... abatementStringstring
... recordedDate ΣI0..1dateTimeDate record was first recorded
... recorder ΣI0..1Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)Who recorded the condition
... asserter ΣI0..1Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)Person who asserts this condition
... stage I0..*BackboneElementStage/grade, usually assessed formally
con-1: Stage SHALL have summary or assessment
.... 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
.... summary I0..1CodeableConceptSimple summary (disease specific)
Binding: ConditionStage (example)
.... assessment I0..*Reference(ClinicalImpression | DiagnosticReport | Observation)Formal record of assessment
.... type I0..1CodeableConceptKind of staging
Binding: ConditionStageType (example)
... evidence I0..*BackboneElementSupporting evidence
con-2: evidence SHALL have code or details
.... 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
.... code ΣI0..*CodeableConceptManifestation/symptom
Binding: ManifestationAndSymptomCodes (example)
.... detail ΣI0..*Reference(Resource)Supporting information found elsewhere
... note I0..*AnnotationAdditional information about the Condition

doco Documentation for this format

Condition

Summary of the Mandatory Requirements

  1. An Encounter Reference in Condition.encounter

Summary of Constraints

  1. Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item
  2. If condition is abated, then clinicalStatus must be either inactive, resolved, or remission
  3. Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error
  4. A code in Condition.category SHOULD be from US Core Condition Category Codes value set.

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Condition I0..*USCoreConditionDetailed information about conditions, problems or diagnoses
... 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 ΣI0..*IdentifierExternal Ids for this condition
... clinicalStatus ?!SΣI0..1CodeableConceptactive | recurrence | relapse | inactive | remission | resolved
Binding: ConditionClinicalStatusCodes (required)
... verificationStatus ?!SΣI0..1CodeableConceptunconfirmed | provisional | differential | confirmed | refuted | entered-in-error
Binding: ConditionVerificationStatus (required)
... category SI1..*CodeableConceptproblem-list-item | encounter-diagnosis | health-concern
Binding: US Core Condition Category Codes (extensible)
... severity I0..1CodeableConceptSubjective severity of condition
Binding: Condition/DiagnosisSeverity (preferred)
... code SΣI1..1CodeableConceptIdentification of the condition, problem or diagnosis
Binding: US Core Condition Code (extensible)
... bodySite ΣI0..*CodeableConceptAnatomical location, if relevant
Binding: SNOMEDCTBodyStructures (example)
... subject SΣI1..1Reference(US Core Patient Profile)Who has the condition?
... encounter SΣI1..1Reference(US Core Encounter Profile) {b}Encounter created as part of
... onset[x] ΣI0..1Estimated or actual date, date-time, or age
.... onsetDateTimedateTime
.... onsetAgeAge
.... onsetPeriodPeriod
.... onsetRangeRange
.... onsetStringstring
... abatement[x] I0..1When in resolution/remission
.... abatementDateTimedateTime
.... abatementAgeAge
.... abatementPeriodPeriod
.... abatementRangeRange
.... abatementStringstring
... recordedDate ΣI0..1dateTimeDate record was first recorded
... recorder ΣI0..1Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)Who recorded the condition
... asserter ΣI0..1Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)Person who asserts this condition
... stage I0..*BackboneElementStage/grade, usually assessed formally
con-1: Stage SHALL have summary or assessment
.... 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
.... summary I0..1CodeableConceptSimple summary (disease specific)
Binding: ConditionStage (example)
.... assessment I0..*Reference(ClinicalImpression | DiagnosticReport | Observation)Formal record of assessment
.... type I0..1CodeableConceptKind of staging
Binding: ConditionStageType (example)
... evidence I0..*BackboneElementSupporting evidence
con-2: evidence SHALL have code or details
.... 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
.... code ΣI0..*CodeableConceptManifestation/symptom
Binding: ManifestationAndSymptomCodes (example)
.... detail ΣI0..*Reference(Resource)Supporting information found elsewhere
... note I0..*AnnotationAdditional information about the Condition

doco Documentation for this format


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