HL7 AWG Project Meeting Minutes
Location: San Antonio
Date: 01/15/18 – 01/17/19
Attendee Names – Also see "2019 Jan AWG Attendance" on Confluence under "AWG Agenda 2019 January"
Mary Lynn Bushman
Mary Kay McDaniel
Pat Van Dyke
Quorum Requirements Met: Yes
Meeting Minutes from Discussion
01/15/19 – Q3
Dental Interoperability Project #1482
01/15/19 – Q4
1. Additional and Supporting Payer/Provider Information (ASPPI)
2. Additional and Supporting Information for Payers/Providers (ASIPP)
Straw poll – 8 for first one 7 for second one. With hyphen in the second
, 11 to 3 for the second one written as "Additional and Supporting Information – Payers/Providers".
ADJOURNED at 4:45 PM.
01/16/19 – Q1
IG Vision on Da Vinci eHealth Record (eCDx/ePDx) for Provider Information Exchange with Payers
01/16/19 – Q2
Russell Ott gave a recap of the guide. The goal is to take ADA requirements (1079 structured format) and codify the data into a CDA document, on behalf of DOD as secondary payers. Thirteen outstanding comments put to a block vote. There was discussion on attachment re-association ID. We will instruct implementers to do the following:
The reason for the difference of location for Attachment Control Number, is that, the produced Attachment in response to a request from a Health Plan is logically similar to a Report being generated in response to an Order (hence inFulfillmentOf.order.id). The Attachment Control Number in an unsolicited submission represents a unique document identifier for the organization generating the Attachment, which is the purpose of the ClinicalDocument.id.
Block vote for comments 4, 5, 6, 7, 8, 9, 17, 18, 28, 32, 35, 40, and 41. Laurie motions to approve sherry seconds. No discussion. No abstentions. All 14 approve.
Lenel announced that a Prior Auth discussion that was done at payer summit would be in the Live Oaks room during Q3. The workgroup agreed to attend the discussions.
Durwin went to Structured Docs discussion about LOINC codes change of "History and Physical" to "Evaluations". Updates will be made on LOINC database by June 2019. Determine impact to current guides for the name change. Document Ontology committee and Structured Docs need to be better coordinated since workgroups were not consulted.
Meeting adjourned at 12:20
01/16/19 – Q3
Q3 – The Da Vinci Project: Authorization Support
Bob Dieterle gave a presentation from the Da Vinci project for authorization support which is one of the use cases. How to make it work in a clinical workflow. Constraints are that it is done by phone, fax, or online
. Anticipating attachment regulation. Per HIPAA, between provider and payer must be x12. No requirement on communication. EMRs do not use x12. Use FHIR to extract data from the eHR and get it to the payer. Make sure that what x12 needs is provided. Use CDS Hooks to provide a card. Make a provision to interact with the provider using SMART on FHIR. Package it up and go into the 275 to give an immediate answer. The medical record verifies that the service is medically necessary. The conversion to the 278 can be done by different methods. Project scope statement for Authorization Support – see PSS under Financial Management in Confluence. See section3.b - Trying to automate the prior auth. By using the 278, attachment regulations are not needed. The 275 is not necessary. Mary Kay says issue with mapping to the 278 cannot come from Financial Management workgroup. There is a reasonable expectation that the attachment regs will come out to support the 275. Is X12 and HL7 coordinating efforts. Viet suggested adding a note that no x12 mapping not to be done by these workgroups. Timeline puts this to 2022. STU to normative. Bob made verbiage changes to the document in the workgroup meeting.
Motion to accept the PSS and second. Passed with 26 approved.
Lenel makes motion and Durwin seconds to vote to co
-sponsor the Da Vinci PSS auth. No further discussion, no abstentions and none opposed. 10 approved.
Mary Lynn submitted list of LOINC codes that could possibly be included in the 277RFI transaction, but it was the wrong list. Workgroup will look at the HIPAA tab and review to see if Dan, with Regenstref needs to be consulted. Will continue the discussion in Q4.
01/16/19 – Q4
277 RFI mapping of LOINC codes
277 RFI mapping of LOINC codes. More than 2000 codes. Some are valid LOINC codes but are not on the Relma tab. Request will be generic to ask for a medical record. A business decision on what is needed. When attachments gets approached regarding LOINC, the workgroup should ask for business justification. Durwin pulled up Regenstref….Documents without imp guides ( like for unstructured) – medical records,
Relma, HIPAA tab with 4 tabs. Documents with imp guides drop down menu with US realm header. Look in CDP1 for the LOINC codes Mary Lynn was looking for. Mary Lynn did not look for the LOINC codes here. Used LOINC code 11503-0 for "medical records" as an example. Not in the HIPAA tab.19002-5 for rehab physical therapy is on the tab. Compared the two. Same attachments class. Ask Dan about this tomorrow. Ask if the search can include all drop downs. Has no HL7 Attachment structure. 18842-5 for discharge summary. Also has an HL7 Attachment structure field. 18682-5 ambulance date was included on the claim so they were not displayed on the HIPAA tab. They have a type 3. 11514-7 chiropractic records total encounter.
Should be able to request these LOINC codes that are not on the HIPAA tab to do the mapping. 11485-0 CMS mapped all codes to LOINC codes, but some were not on the HIPAA tab. 11526-1 pathology study. 19004-1, skilled nursing is for rehab. Motion to ask Dan to add no IG on these. Laurie motion to move forward, Mary Lynn second. Discussion – Laurie requests that we have a work instruction for them to have a business reason/justification and be prepared. None abstain
, all in favor - 14 approved. Follow-up with Tony to see if he also has some codes. Lorraine left NCVHS update. Interoperability predictability roadmap hearing to create a letter that will go to CMS. Regulation and standards recommendations Feb 6 & 7. Present to the full committee at NCVHS. Mentioned being innovative using standards you must have trading partner agreements is allowed with BAA mutually agreed upon. There will be clarification in the letter to what will be allowed.
Discussion about APIs being adopted by top eHR vendors and payers. However, there are so many providers that do not go through the top eHR vendors.
Medicare Attachments - Mary Lynn has implemented 180 providers set up for using 275. Receiving 275s every day. Over 900 275s in Dec. that include structured OP notes and unstructured documents.
Lenel - Allscripts e-charts H & P.
Keith – No news on the attachment regulation, but heard that it was sitting in OMB and is in process.
Rescinding the health plan ID (HPID). Open for comment period.
ADJOURNED at 4:41 PM.
01/17/19 – Q1
Reminder to check in Confluence and do attendance.
Russ Ott is the new co-chair.
Joint meeting with Financial Management workgroup. Mary Kay is a TSC liaison to Da Vinci. There are 7 implementation guides coming up for ballot in May. Two are co-sponsored by Attachments. Reconciliation and quality of the guides will take time to review. Content is still being added. By 03/25/19, we have to approve the guides in a short deal of time. Combine the Financial Management and Attachment calls to review imp guides for ePDx, Auth and CRD. Do not map to x12 278 because it is not widely used. The FHIR auth resource should match the business needs. The state of Virginia is using Standardized Episodes of Care (SEOC) codes that are specific to them. Discussion of FHIR can adapt to business needs as they become known, such as in Virginia. There is a challenge when something is done during the encounter that was not on the auth. US Realm auths are specific to what was approved on the auth. No matter the use case, FHIR will try to support it.
Mary kay met with the TSC and submitted the form for the name change. After 30 days, they then give approval.
FHIR R4 is the current version web and imp guide. List of resources; eligibility, claims, predetermination, if a person is not eligible, then other resources response back will let you know if person is not covered. You do not have to do a separate eligibility. Discussion of FHIR transactions providing only what is available in internal systems. Pre-auths are normally required for more complicated procedures than is common. May not be automated as easily as claims. Pharmacies and vision would have different perspectives than dental and medical regarding when a pre-auth is needed. FHIR restful API resources can be used behind the scenes using PUT or GET commands. The FHIR resources between entities, ensures that you will get a response. Paul talked about differences in US vs other countries. Relative order of use section. Overview of claim resource. UML diagram of a claim model. Paul suggested separate pre-auths for inpatient, dental, vision, pharmacy and what would go into a profile. The US uses DRG codes, but for global there may be a package code. The structure is there to make the rules you will need. Service type codes will be used in an auth. Have a fundamental base that can handle most business needs to do a pre-auth. The claim must contain the preauthorization code. The detail line items do not work well for pharmacy or vision. The detail, then sub detail for compound drugs is an example. One pre-auth guide with multiple profiles to handle the multiple claim types (dental, vision, inpatient, ambulance, pharmacy, etc.). Must align business with technical. Everything requires maintenance. First timer question. Paul showed the model. Where to go to get your business need into a profile. Go to Financial Management workgroup. HL7 has events she can join. Da Vinci can put some of that together. Weekly calls with FM at 11 EST. Meeting in Montreal would be best to discuss/finalize the imp guides for ballot: Mon 1-4, Tues 3-4, W 3-4, TH 3-4.
01/17/19 – Q2
Value Based Health Story
Cross-Paradigm Story Board Artifact: Payer Perspective, Value-Based Care reconciliation.
AWG Confluence Page updates and training
Adjourned at 12:00
Supporting Documents: Documents can be found in the corresponding Confluence pages for each workgroup or subject.
29 Jan 2019
Dial-in Number: (605) 472-5483 - (US)
Access Code: 161405
Join the Online Meeting: