Skip to end of metadata
Go to start of metadata

Publication Request

Publication Request

1. Published Name of the Standard for which request is being made

Da Vinci Unsolicited Notifications 1.0.0 - STU1 Release

2. Standards Material/Document

STU

3. Date of Request

Aug 27, 2020

4. Use Period

2 years

5. Reason for extension, timeline, and actions

6. Original Publication Date

7. End date of the current STU period

8. Length of the requested extension

9. Review Process

10. HL7 Work Group making this request and date

Infrastructure And Messaging Work Group (InM)

10a. Requesting WG Date

Aug 27, 2020

11. URL of approval minutes

https://confluence.hl7.org/pages/viewpage.action?pageId=91984682

12. HL7 Product Management Group

FHIR

12a. Management Group Date of Approval

Sep 02, 2020

13. URL of approval minutes

https://confluence.hl7.org/pages/viewpage.action?pageId=91985985

14. Is the artifact ready for final publication?

Yes

15. If not ready, please describe remaining steps.

16. Tool name used to produce the machine processable artifacts in the IG

Spreadsheets - SD
XML hand editing - value sets
YAML (hand editing) - IG, SD, codesystem
Custom Python script - CapabilityStatements

17. The name of the “IG artifact” within the context of the above mentioned tool.

18. Balloted Name of the standard for which request is being made

HL7 FHIR® Implementation Guide: Alerts, Release 1- US Realm

19. Requested name for published standard

Da Vinci Unsolicited Notifications 1.0.0 - STU1 Release

20. If CMET, list IDs balloted

21. Project Insight Number

1516

22. Document Realm

US

23. Ballot cycle in which the document was successfully balloted

2020-feb

24. Results of that ballot (following reconciliation activities):

24. Results of that ballot (following reconciliation activities):

(not needed for errata, STU extension, or unballoted STU update)

25. Affirmative

80

26. Negative

29

27. Abstentions

38

28. Not Returned

24

29. Total in ballot pool

172

30. Date on which final document/standards material was supplied to HQ

Sep 21, 2020

31. URL of publication material/ SVN repository

https://github.com/HL7/davinci-alerts/

32. Publishing Facilitator

Eric Haas

33. Special Publication Instructions

34. URL of ballot reconciliation document

http://www.hl7.org/documentcenter/public/ballots/2020FEB/reconciliation/recon_fhir_ig_alerts_r1_d1_2020feb.xls

35. Has the Work Group posted its consideration of all comments received in its reconciliation document on the ballot desktop?

Yes

36. Substantive Changes Since Last Ballot?

Yes

37. Product Brief Reviewed By

InM Wg

38. Date Product Brief Reviewed

Aug 27, 2020

39. Has the Product Brief changed?

Product Brief

Product Brief

40. Family

FHIR

41. Section

Implementation Guides

42. Topic

Patient Care

43. Please Describe the Topic

44. Product Type

Implementation Guide

45. Parent standard

FHIR R4

46. Parent Standard Status

Active

47. Update/replace standard

NA

48. Common name/search keyword

Da Vinci Alerts, Da Vinci Notifications, Da Vinci Unsolicited Notifications, Alerts, Notifications, Unsolicited Notifications

49. Description

This implementation guide describes a framework method for the communication of relevant notifications to support the real-time exchange of information that impacts patient care and value based or risk based services. Providers and Payers may need to be notified when activities occur that impact a patient’s care. This may be as traditional as a notification of an admission or transfer to or discharge from a care setting. It also includes notifications about changes in treatment such as a new or different medication, or changes in patient status like a new diagnosis. These notifications provide information that can improve care management and care coordination as well as act as the trigger for quality programs and other patient focused activities (for example, risk adjustment). By allowing the patient’s healthcare providers to be better informed and able to take actions and intervene earlier, the twin goals of better patient care and reduced cost of care may be met.

Targets

Targets

These are categories of potential users, implementers, or other interested parties such as those that are indicated on the Project Scope Statement under “Stakeholders/Vendors/Providers”. Select those that are applicable, or suggest others:

50. Stakeholders

Clinical and Public Health Laboratories, Immunization Registries, Quality Reporting Agencies, Regulatory Agency, Payors, Other (specify in text box below)

51. Vendors

Pharmaceutical, EHR, PHR, Equipment, Health Care IT, Clinical Decision Support Systems, Lab, HIS

52. Providers

Clinical and Public Health Laboratories Emergency Services Local and State Departments of Health Medical Imaging Service Healthcare Institutions (hospitals, long term care, home care, mental health)

53. Benefits

This Guide defines a FHIR messaging based paradigm and framework to establish consistently adoptable and reproducible methods to exchange notifications. This framework supports the patient admission, transfer, and discharge events to generate unsolicited notifications to the care team.

54. Implementations/Case Studies

55. Development Background

This Implementation Guide is supported by the Da Vinci initiative which is a private effort to accelerate the adoption of Health Level Seven International Fast Healthcare Interoperability Resources (HL7® FHIR®) as the standard to support and integrate value-based care (VBC) data exchange across communities. Like all Da Vinci Implementation Guides, it follows the HL7 Da Vinci Guiding Principles for exchange of patient health information. The guide is based upon the prior work from the US Core and Da Vinci Health Record Exchange (HRex) Implementation Guides. Changes to this specification are managed by the sponsoring HL7 Infrastructure and Messaging (INM) workgroup and are incorporated as part of the standard HL7 balloting process.







1 Comment

  1. For #50: I was going to add Healthcare Institutions and Providers, but don;t see a text box to enter this in (And why are those not listed under stakeholders?)