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

Risk Based Contracts Member Attribution (ATR) List

2. Standards Material/Document

STU

3. Date of Request

Dec 16, 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

Financial Management

10a. Requesting WG Date

Oct 20, 2020

11. URL of approval minutes

https://confluence.hl7.org/display/FM/2020-10-20+FM+Interim+Meeting

12. HL7 Product Management Group

FMG

12a. Management Group Date of Approval

Dec 16, 2020

13. URL of approval minutes

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

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

FHIR IG Publisher - hand edit

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

DaVinci-ATR

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

HL7 FHIR® Implementation Guide: Risk Based Contract Member Identification, Release 1 - US Realm

19. Requested name for published standard

HL7 FHIR® Implementation Guide: Risk Based Contract Member Identification, Release 1 - US Realm

20. If CMET, list IDs balloted

N/A

21. Project Insight Number

1517

22. Document Realm

US Realm

23. Ballot cycle in which the document was successfully balloted

2020-02

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

64

26. Negative

14

27. Abstentions

53

28. Not Returned

21

29. Total in ballot pool

152

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

Dec 16, 2020

31. URL of publication material/ SVN repository

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

32. Publishing Facilitator

Nagesh (Dragon) Bashyam

33. Special Publication Instructions

34. URL of ballot reconciliation document

http://www.hl7.org/documentcenter/public/ballots/2020FEB/reconciliation/recon_fhir_ig_risk_contract_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?

37. Product Brief Reviewed By

Financial Management

38. Date Product Brief Reviewed

Dec 01, 2020

39. Has the Product Brief changed?

Product Brief

Product Brief

40. Family

FHIR

41. Section

Implementation Guides

42. Topic

Financial Management

43. Please Describe the Topic

Member attribution list electronic exchange implementation guide.

44. Product Type

Implementation Guide

45. Parent standard

FHIR R4

46. Parent Standard Status

Active

47. Update/replace standard

N/A

48. Common name/search keyword

Member Attribution, Member Roster, Risk based,

49. Description

The implementation guide defines the mechanisms, resources, profiles and extensions required to exchange Member Attribution Lists. The Member Attribution Lists enable providers and payer organization to validate enrollment in Value-Based Care (VBC) programs and support reporting requirements and payment reconciliation.

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

Payors

51. Vendors

EHR, PHR, Health Care IT

52. Providers

Healthcare Institutions (hospitals, long term care, home care, mental health) Other (specify in text box below)

53. Benefits

Enables FHIR based exchange of Member Attribution Lists (MAL) between providers and payers.

Replaces the fragile current methods of custom files (CSVs, txt etc) and exchanging them using different methods such as Email and Secure Eile Transfer Protocol (SFTP)

54. Implementations/Case Studies

MultiCare
Providence
Epic

55. Development Background