Stream: connectathon mgmt
Topic: PCDE Track
May Terry (May 06 2020 at 17:48):
For Payer Coverage Decision Exchange Connectathon activities.
May Terry (May 06 2020 at 17:50):
URL for May 2020 PCDE Track description and scenarios: https://confluence.hl7.org/pages/viewpage.action?pageId=80119097
May Terry (May 13 2020 at 14:48):
@Sreekanth Puram and other PCDE participants - we made updates to the $member-match documentation. Please note this for the PCDE track. https://confluence.hl7.org/display/DVP/HL7+Da+Vinci+PDex+%24member-match.
May Terry (May 13 2020 at 14:53):
@Sreekanth Puram and @Joe Minieri - Sample patient data supporting the PCDE $member-match scenario is available on the PDex Reference implementation page: https://confluence.hl7.org/display/DVP/Member-Match+Reference+Implementation. The example FHIR patient that will have the PCDE diabetes bundle example will be Joshua Williams: UMB dh-10106. I'll post this later today.
Sreekanth Puram (May 13 2020 at 16:35):
Is the client available anywhere so that my team can test out the solution.
May Terry (May 13 2020 at 17:13):
@Sreekanth Puram - The MITRE client is currently undergoing changes to address $member-match changes discussed last Friday. @Joe Minieri can reach out to you when that is available to test.
Sreekanth Puram (May 13 2020 at 17:18):
ok
Sreekanth Puram (May 13 2020 at 19:37):
@May Terry I see that there is a discrepency in the membermatch explanation and example
Sreekanth Puram (May 13 2020 at 19:39):
Explanation says that the identifier of type "MB" should be specified for coverage where as the example says that "MB" identifier assigned to a patient. I guess it should be assigned to patient. Let me know if this is wrong.
May Terry (May 13 2020 at 19:43):
I think it works this way, although cc'ing @Mark Scrimshire and @Robert Dieterle to confirm.
If it's for the inital $member-match from the new health plan then the MB for the Patient should be of the old health plan with the system related to the old health plan. Any MBs within the Coverage resource are relative to the plan for which it belongs. So the old coverage should have the MB from the old health plan and new coverage should have an MB from the new health plan.
Sreekanth Puram (May 13 2020 at 19:51):
I thought we decided that the old coverage information will be used for reference for the old payer to identify the member. However the MB type is assigned to the patient when requested $membermatch by the new payer and UMB is assigned by the old payer again to the patient resource
May Terry (May 13 2020 at 20:03):
@Mark Scrimshire and @Robert Dieterle - please reply to @Sreekanth Puram 's question. Seems like this changes by the day and I don't want to misrepresent it.
May Terry (May 13 2020 at 20:06):
My understanding is that the client is sending the old health MB identifier, which you should find in the old health plan Coverage resource, AND included in the Patient resource, which is used to lookup the old MB. The parameter return by the old health plan will have a Patient resource that includes the new UMB to the identifier type and the new health plan coverage resouce that is preserved "as-is" by whatever is submitted by the new health plan. So I'm not sure what the issue is...
May Terry (May 13 2020 at 20:10):
you'll be receiving from the client (representing the new health plan) 3 embedded resources in the Parameter request: the Patient, which has the MB from the old health plan, the old coverage resource which contains the MB from the old health plan, and a new coverage resource which contains the MB from the new health plan.
Sreekanth Puram (May 13 2020 at 20:26):
Yes. I think we are saying the samething but the example does not reflect the same.
May Terry (May 13 2020 at 20:26):
ah...okay. Let me see about revising that. Thanks!
Gregory Zeller (May 13 2020 at 20:29):
I will sign onto Zoom now.
May Terry (May 13 2020 at 20:47):
@Sreekanth Puram - updated the Parameter example. lmk if this lines up with our understanding. thanks!
Sreekanth Puram (May 13 2020 at 20:53):
Technically this can work but am wondering why we need to duplicate MB
Robert Dieterle (May 13 2020 at 20:59):
May is correct.
Bob
Robert Dieterle (May 13 2020 at 21:07):
The member ID in the old plan coverage resource (coverage.identifier) is labeled as MB to identify it as the old plan member ID.
The old plan returns the universal member id in the new plan patient resource as an identifier (patient.identifier) labeled as UMB.
Last change was to move the UMB from the old plan coverage resource to the new plan patient resource (as recommended by Paul K).
Regards,
Bob
May Terry (May 14 2020 at 01:04):
@Sreekanth Puram and @Joe Minieri - here's the diabetes PCDE example: https://confluence.hl7.org/download/attachments/80119097/Bundle-pcde-example-diabetes_RH.xml?version=1&modificationDate=1589418146254&api=v2. It's in XML but I suppose you can convert it to JSON doing a GET after POSTing it to the FHIR servers.
May Terry (May 14 2020 at 01:06):
I had to use a different patient example. It's now changed from Carol Williams to Robert Hill. Reason was because it was one of the example patients in the $member-match RI and has examples for patient and coverage.
Mark Scrimshire (May 14 2020 at 03:48):
@May Terry I have modified member-match and published to http://ec2-18-223-117-133.us-east-2.compute.amazonaws.com:8000/v1/profhirler/Patient/$member-match (this links through to the Logica Health sandbox https://api.logicahealth.org/DVPDexR4Payer1/open. The Member Match will return a 422 when a match fails. This version also creates a uniqueMemberId parameter in the response which holds the old plan's member number. I also removed the first parameter ("exact") which isn't used.
May Terry (May 14 2020 at 14:52):
Having some problems with getting the Task Zoom call open. Let's keep the Task dialogue on this stream in the meantime. I'll notify the participants once that's up and running.
Dave Hamill (May 14 2020 at 15:10):
May Terry said:
Having some problems with getting the Task Zoom call open. Let's keep the Task dialogue on this stream in the meantime. I'll notify the participants once that's up and running.
Is there any assistance you need with Zoom?
May Terry (May 14 2020 at 15:15):
@Joe Minieri successfully started the Zoom. we're good to go. Thanks @Dave Hamill !
May Terry (May 14 2020 at 15:17):
For PCDE "Task sub-scenario" discussions, use this Zoom link: https://zoom.us/j/9661749588
For $member-match sub-scenario discussions, use the PDex Zoom link: https://zoom.us/j/2779458846
Sreekanth Puram (May 14 2020 at 15:19):
I will post my endpoint in an hour. Is that fine?
Sreekanth Puram (May 14 2020 at 15:19):
we are just trying it out
May Terry (May 14 2020 at 15:35):
@Joe Minieri - would it be possible to try the PCDE client with Sreekanth's server when it's available? If not then I suppose we can try it with Postman.
Joe Minieri (May 14 2020 at 15:46):
It is possible. The messages that can be send are a bit limited but I could modify them further. The client I have set up allows for a end point to be specified
Sreekanth Puram (May 14 2020 at 15:52):
I have a client also
May Terry (May 14 2020 at 15:53):
Great! :-)
May Terry (May 14 2020 at 15:54):
would be great to show a "mix and match" of different clients and servers so @Sreekanth Puram - would it be possible to point your client to Joe's server if he gave you an example Parameter for the request?
May Terry (May 14 2020 at 15:55):
reason...looks like the Patient examples for $member-match are different in Joe's RI and vice versa.
Sreekanth Puram (May 14 2020 at 15:57):
Yes we can do that
Sreekanth Puram (May 14 2020 at 15:57):
give us a few minutes
Sreekanth Puram (May 14 2020 at 16:25):
https://sm.mettles.com/payerfhir/hapi-fhir-jpaserver/fhir/Patient/$member-match
Sreekanth Puram (May 14 2020 at 16:25):
This our member match
Sreekanth Puram (May 14 2020 at 16:25):
endpoint
Sreekanth Puram (May 14 2020 at 16:25):
you can run the member match on the list given on the connectathon page
Sreekanth Puram (May 14 2020 at 16:25):
https://sm.mettles.com/payerfhir/hapi-fhir-jpaserver/fhir/Task
Sreekanth Puram (May 14 2020 at 16:26):
You can post a Bundle request ehre
Sreekanth Puram (May 14 2020 at 16:26):
here*
May Terry (May 14 2020 at 16:37):
@Joe Minieri :point_of_information:
Joe Minieri (May 14 2020 at 16:38):
I'm looking at it now
Sreekanth Puram (May 14 2020 at 16:46):
Sreekanth Puram said:
You can post a Bundle request ehre
I meant post a PCDE request as a task :)
Joe Minieri (May 14 2020 at 16:49):
Which patients should I be testing with for member match?
Sreekanth Puram (May 14 2020 at 16:51):
The sample patients given in the Track
Sreekanth Puram (May 14 2020 at 16:51):
description
Sreekanth Puram (May 14 2020 at 16:51):
There were a few Json files right
Joe Minieri (May 14 2020 at 17:01):
I've tried a few different patients. I'm not sure if they are the right ones, but I am getting 200 responses, but none of them have UMBs. I have to drop of for about an hour but I can do more testing when I get back
Sreekanth Puram (May 14 2020 at 17:03):
Oh
Sreekanth Puram (May 14 2020 at 17:03):
can you post the
Sreekanth Puram (May 14 2020 at 17:03):
content here once
May Terry (May 14 2020 at 17:04):
we're reconvening on the $member-match zoom channel now (1p) - use the PDex Zoom link: https://zoom.us/j/2779458846
Sreekanth Puram (May 14 2020 at 17:04):
I am in a different call
Sreekanth Puram (May 14 2020 at 17:05):
I will join in some time
Mark Scrimshire (May 14 2020 at 17:21):
Sync up for Member-match operation at 3:30 on the PDEX Zoom
Joe Minieri (May 14 2020 at 18:28):
test_member-match.json
This is a sample message that I tried sending
Sreekanth Puram (May 14 2020 at 18:33):
My team is checking into that
Sreekanth Puram (May 14 2020 at 18:35):
Joe Minieri said:
test_member-match.json
This is a sample message that I tried sending
Sreekanth Puram (May 14 2020 at 18:36):
Can you try once again
Sreekanth Puram (May 14 2020 at 18:53):
@Joe Minieri did you get a chance to try?
Joe Minieri (May 14 2020 at 18:56):
I tried it again. I now get a 404 which I think is the correct response if you don't have that patient loaded
Sreekanth Puram (May 14 2020 at 19:21):
Can you try these cases
Sreekanth Puram (May 14 2020 at 19:21):
Coverage Identifier : DH10001236
Patient : Robert Hill
Sreekanth Puram (May 14 2020 at 19:22):
2 , Coverage Identifier : DH10001234 , Patient : Patricia Ann
3, Coverage Identifier : DH10001235 , Patient : Joseph Ross
Sreekanth Puram (May 14 2020 at 19:22):
The details are in <Coverage identifier>.json
Sreekanth Puram (May 14 2020 at 19:28):
4, file : DH10001237.json , Coverage Identifier : DH10001237 , patient : Patrick Person G.
Joe Minieri (May 14 2020 at 19:34):
The identifiers you sent are the FHIR ids for those patients. The identifiers are different. I don't have mine set up right now to work with those but I can test it separately
Sreekanth Puram (May 14 2020 at 19:35):
I was just giving you the link to the json
Sreekanth Puram (May 14 2020 at 20:29):
@Joe Minieri did you get lucky sending in the task
Joe Minieri (May 14 2020 at 20:30):
I was able to successfully post the task and I got a task created response back. I haven't tried polling it to see if I can get the bundle as I am not sure of the correct input for that
Sreekanth Puram (May 14 2020 at 20:45):
Hi Joe, we Updated the status
Sreekanth Puram (May 14 2020 at 20:45):
Can you check
Sreekanth Puram (May 14 2020 at 20:45):
the Bundle
Joe Minieri (May 14 2020 at 20:47):
Do you know what I need to send to your endpoint to poll it?
Joe Minieri (May 14 2020 at 20:49):
The focus for tomorrow is going to be on this process as well. Not sure if you were on the PDex call when we discussed it but we are going to flesh out the process more tomorrow
Sreekanth Puram (May 14 2020 at 20:51):
Just a get call on the Task
Sreekanth Puram (May 14 2020 at 20:51):
if the status shows complete, you need to check for the output
Sreekanth Puram (May 14 2020 at 20:51):
and you can see the data
May Terry (May 14 2020 at 20:52):
We're planning on having an ad-hoc birds of a feather session to discuss expected HTTP response codes for the Task resource...Friday, 10:15a-10:45a EST on PCDE "Task sub-scenario" discussions, use this Zoom link: https://zoom.us/j/9661749588.
May Terry (May 14 2020 at 20:52):
@Sreekanth Puram and @Robert Dieterle - would you both be able to join? We need your input for this meeting.
Joe Minieri (May 14 2020 at 21:00):
@Sreekanth Puram I was able to get the bundle from the successful task.
Joe Minieri (May 14 2020 at 21:01):
I will work on updating my client to be able to handle the process
Sreekanth Puram (May 14 2020 at 21:03):
@May Terry is the meeting still on
Sreekanth Puram (May 14 2020 at 21:03):
I can join
May Terry (May 14 2020 at 21:04):
the PDEx/PCDE wrap-up just ended, but Mark is still on for anyone who has questions. We'll be reconvening tomorrow at 10:15a for the PCDE Task discussion on the PCDE Zoom link: https://zoom.us/j/9661749588.
May Terry (May 14 2020 at 21:06):
but...overall, a lot was accomplished today! :tada:
thanks to @Sreekanth Puram , @Joe Minieri , and @Mark Scrimshire , we were able to test calls from clients to the Mettles RI for $member-match, and for Task. We should be able to present and record demos in the Friday wrap-up. We can discuss a time to try a dry-run for the recordings during our Task discussion at 10:15a.
May Terry (May 14 2020 at 21:07):
great job, PCDE-ers! :smiley:
Sandy Vance (May 14 2020 at 21:29):
May Terry said:
but...overall, a lot was accomplished today! :tada:
thanks to Sreekanth Puram , Joe Minieri , and Mark Scrimshire , we were able to test calls from clients to the Mettles RI for $member-match, and for Task. We should be able to present and record demos in the Friday wrap-up. We can discuss a time to try a dry-run for the recordings during our Task discussion at 10:15a.
Nice! Don't forget to schedule your recorded wrap up here https://docs.google.com/spreadsheets/d/1P4EPT2Hi3PI9eB-TYPj5xYHzInZS4ixd/edit#gid=443913853
May Terry (May 14 2020 at 21:31):
@Sandra Vance - we'll be doing our wrap-up with PDEx so I'll need to coordinate with @Mark Scrimshire to find a time tomorrow.
Mark Scrimshire (May 14 2020 at 22:08):
May Terry said:
Sandra Vance - we'll be doing our wrap-up with PDEx so I'll need to coordinate with Mark Scrimshire to find a time tomorrow.
Mark Scrimshire: The $member-match specification has been updated to reflect the discussions and deliberations from Day 1 of the Connectathon as a result of testing the $member-match operation: https://confluence.hl7.org/display/DVP/HL7+Da+Vinci+PDex+%24member-match
Mark Scrimshire (May 14 2020 at 22:12):
@May Terry Shall we grab 12:00 to 12:15 on the main schedule for PDEX/PCDE demo tomorrow?
May Terry (May 14 2020 at 22:14):
Sure. 12-12:15 works!
Mark Scrimshire said:
May Terry Shall we grab 12:00 to 12:15 on the main schedule for PDEX/PCDE demo tomorrow?
Mark Scrimshire (May 14 2020 at 22:28):
May Terry said:
Sure. 12-12:15 works!
Done!
Sreekanth Puram (May 15 2020 at 12:18):
@May Terry we can do the demo at 12. I have the server and the GUI working. Let me know if you want us to use our client too.
Sreekanth Puram (May 15 2020 at 12:20):
I had a chat with with @Patrick Haren from Cigna last night. He says that the "MB" identifier should be associated with Patient and not with Coverage. I think we can go with what ever we have for today and have a discussion in PDEX/PCDE friday calls and decide on these
May Terry (May 15 2020 at 12:36):
@Sreekanth Puram I think 12-12:15p is our report-out. 4:30 is scheduled for demos for PDEx and PCDE. cc: @Mark Scrimshire to confirm. Unfortunately, that happens at the same time as Gaps in Care demos. Will that be a problem?
Sreekanth Puram said:
May Terry we can do the demo at 12. I have the server and the GUI working. Let me know if you want us to use our client too.
Sreekanth Puram (May 15 2020 at 12:51):
I may have to be there at the Gaps in care one if they are doing a demo there. However my demo is straightforward, @Kishore A Metla and @Melanie Combs-Dyer will represent me. Kishore will do the demo or you can do it too. I don't think it will be an issue.
Patrick Haren (May 15 2020 at 13:09):
@May Terry @Sreekanth Puram . The question is on the choice of where to place member numbers. The Patient resource typically holds business identifiers related to the person's record in the system (in this case the payer system). We seem to be using it for that in some cases, but are placing it in a Coverage resource in other cases, within this implementation. A business identifier in a resource is something that identifies the resource, so shouldn't that apply to a Coverage resource as well? i.e. does an MB uniquely identify the Coverage, or doesn't it really identify the Patient (member record)?
May Terry (May 15 2020 at 13:10):
@Patrick Haren - not sure where it deviated in testing yesterday, but my assumption is that the old health plan member identifier should be in 1) Patient parameter, and 2) in the old health plan coverage parameter. If none of the RIs accept this, then we need to refactor them.
Patrick Haren (May 15 2020 at 13:22):
we can do this for connect-a-thon, but, ultimately we need to refactor the guidance.
Patrick Haren (May 15 2020 at 13:24):
for example, simply use the 'beneficiary' field in Coverage, to reference the Patient (member)
May Terry (May 15 2020 at 13:28):
we definitely want to hear how it can be improved, but it probably merits further discussion rather than just changing this. It is possible for Patient to have multiple identifier types and if you have beneficiary referencing just Patient then you have one more level of indirection to look for an identifier type of MB (since Patient can have multiple identifier types). Seems like extra complexity that probably needs some agreement and consensus.
May Terry (May 15 2020 at 14:21):
ALL - still having problems setting up the host for Zoom...our Task discussion will start in 5 min on the PCDE Zoom.
Mark Scrimshire (May 15 2020 at 14:21):
May Terry said:
ALL - still having problems setting up the host for Zoom...our Task discussion will start in 5 min on the PCDE Zoom.
PDEX zoom is quiet if you want to take that over.
May Terry (May 15 2020 at 14:22):
ah...I suppose that'll work. ALL - let's switch over to the PDEx zoom for the Task discussion.
May Terry (May 15 2020 at 14:29):
All, please join the PDex Zoom: https://zoom.us/j/2779458846 for discussion on Task error handling.
May Terry (May 15 2020 at 15:26):
@Sreekanth Puram - looks like we will be showing some short demos at noon. We're currently discussing specifics on the PDEx channel if you'd like to join: https://zoom.us/j/2779458846
May Terry (May 15 2020 at 16:44):
Great job on the demos @Joe Minieri and @Sreekanth Puram ! :tada:
Sreekanth Puram (May 15 2020 at 20:16):
@May Terry I will be skipping the PCDE demo to DaVinci. Kishore or Melanie will be there from my side. But I think @Joe Minieri has my demo. so he can take care right?
Joe Minieri (May 15 2020 at 20:16):
Yes. I will be demoing again just like the previous one
Sreekanth Puram (May 15 2020 at 20:17):
good luck
Sreekanth Puram (May 15 2020 at 20:19):
which zoom meeting is it going to be in?
Sreekanth Puram (May 15 2020 at 20:19):
Mark Scrimshire (May 15 2020 at 20:19):
I Want to give a shout out to everyone who has contributed to the PDEX/PCDE Track. We have progressed the specifications in important ways in these last two days. The $member-match function is an important operation that I am positive will get significant use once implemented.
Sreekanth Puram (May 15 2020 at 20:20):
@Mark Scrimshire is this the dial in for the zoom call? https://zoom.us/j/2779458846
Sreekanth Puram (May 15 2020 at 20:20):
where you report out to DaVinci
Mark Scrimshire (May 15 2020 at 20:29):
Sreekanth Puram said:
Mark Scrimshire is this the dial in for the zoom call? https://zoom.us/j/2779458846
Decision Exchange (PCDE)
https://zoom.us/j/2779458846. Yes
Mark Scrimshire (May 15 2020 at 20:33):
Sreekanth Puram said:
Mark Scrimshire is this the dial in for the zoom call? https://zoom.us/j/2779458846
YEs
May Terry (May 15 2020 at 22:22):
Thanks all for participating in the PCDE Track at Connectathon 24!
PCDE report out notes are located here: https://docs.google.com/document/d/1B6FvP5IP83tuUPvOMQjZIR5jYyw4OSbahgRqnbkPZZ8/edit#heading=h.fkgawwpm79yn
Douglas DeShazo (Aug 27 2020 at 18:57):
For the upcoming Connectathon HRex/CDex/PCDE - track is there a link to the Mitre RI that @Lloyd McKenzie mentioned in the kick off recordings?
Lloyd McKenzie (Aug 27 2020 at 20:41):
@Nikolai Schwertner ?
Nikolai Schwertner (Aug 28 2020 at 21:14):
If the questions is about the CDex reference implementation, we are currently updating it to conform to the proposed Task poll model for the upcoming connectathon. This will be available at https://sandbox.logicahealth.org/DaVinciCDexPayerV2 and https://sandbox.logicahealth.org/DaVinciCDexProviderV2 shortly. All who had access to the previous reference implementation (https://sandbox.logicahealth.org/DaVinciCDexPayer and https://sandbox.logicahealth.org/DaVinciCDexProvider) will receive invitations to the new set of sandboxes. Everyone else will need to request access at the connectathon or via PM to me.
Ron Urwongse (Sep 02 2020 at 13:40):
Hi All - Ron Urwongse here from CAQH. Will be participating in Connectathon next week. May and Lloyd and I were discussing on an e-mail thread that we're taking here, on the possibility of incorporating endpoint directory and querying as part of the PCDE Track. Just taking a straw poll here for those who are participating in PCDE Track, how useful it would be to incorporate a step where "new" health plan queries endpoint directory for metadata on "old" health plans endpoints? Thanks, Ron
May Terry (Sep 09 2020 at 16:03):
Hi all! Here is the FHIR Connectathon 25 DaVinci HRex/CDex/PCDE Track page: https://confluence.hl7.org/pages/viewpage.action?pageId=86975727
We welcome both technical and SMEs to our track. For those who are observers and not familiar with PCDE, we'll be providing a PCDE Overview and Walkthrough presentation on Thursday morning as part of our track kick-off. Slides are available here: https://confluence.hl7.org/download/attachments/86975727/Connectathon-25-PCDE-Overview-Walkthrough.pptx?version=1&modificationDate=1599667021475&api=v2.
Feel free to ask questions or provide feedback ahead of time.
Thanks!
@Joe Minieri and @May Terry (PCDE sub-track co-leads).
Lloyd McKenzie (Sep 09 2020 at 21:25):
Note that kick-off for the track will be happening tomorrow. PCDE overview, walkthrough and planning will start at 9am. HRex/CDex will follow at 10am
May Terry (Sep 10 2020 at 12:19):
Quick FYI: Today's PCDE Overview has moved from the breakout room to the main HRex/CDex/PCDE track Zoom meeting.
Sreekanth Puram (Sep 10 2020 at 12:24):
May, Do you have a sample patient bundle which contains the careplans, priorauthorizations etc that we can exchange between payers?
Ron Urwongse (Sep 10 2020 at 12:30):
Looking forward to connecting with all on the track.
Sreekanth Puram (Sep 10 2020 at 12:41):
Ron Urwongse said:
Looking forward to connecting with all on the track.
Hi @Ron Urwongse , I was trying to test the Postman collection for your endpoint directory, what is the hostname that I need to use?
Ron Urwongse (Sep 10 2020 at 12:48):
Hi Sreekanth, I can send you the 1-pager via e-mail. To search (once you have API creds), you can use a. https://fds.collablynk.com/api/fds/endpoints
Ron Urwongse (Sep 10 2020 at 12:48):
but I can send you the API creds via e-mail. If anybody else is interested in them, I can make available too.
Ron Urwongse (Sep 10 2020 at 12:49):
@Sreekanth Puram , do you want us to load the endpoints described in PCDE track scenario, so that you can query them?
Sreekanth Puram (Sep 10 2020 at 12:51):
Ron Urwongse said:
Hi Sreekanth, I can send you the 1-pager via e-mail. To search (once you have API creds), you can use a. https://fds.collablynk.com/api/fds/endpoints
I already have the credentials and the one pager. So I can test it.
Ron Urwongse (Sep 10 2020 at 13:04):
Are the endpoints to load for Maryland Capital Insurance described here: https://touchstone.aegis.net/touchstone/testdefinitions?selectedTestGrp=/FHIRSandbox/DaVinci/FHIR4-0-1-Test/HREX&activeOnly=true&contentEntry=TEST_SCRIPTS ?
Ron Urwongse (Sep 10 2020 at 13:08):
nevermind, i think those are just the test scripts
Ron Urwongse (Sep 10 2020 at 13:24):
Hi @Sreekanth Puram , do you know if the test servers were posted for this track? I don't see them on the Confluence.
Sreekanth Puram (Sep 10 2020 at 13:27):
I don't think there are any test servers posted for this track. However by the afternoon, we will have a few endpoints that you can include. In addition to this, I have some Prior auth and Gaps in care endpoints that I can pass on
Ron Urwongse (Sep 10 2020 at 13:30):
Thanks Sreekanth
Ron Urwongse (Sep 10 2020 at 14:14):
By the way, the default server https://davinci-pcde-ri.logicahealth.org/fhir is recorded in the endpoint directory. So it's available if you want to test the endpoint discovery step preceding the member match and PCDE request steps. You can search for 'Payer Coverage Decision Exchange' as parameter. Instructions-to-access-Endpoint-directory.docx
May Terry (Sep 10 2020 at 14:24):
Sreekanth Puram said:
May, Do you have a sample patient bundle which contains the careplans, priorauthorizations etc that we can exchange between payers?
@Sreekanth Puram - try this PCDE Bundle example which has an embedded EDI 278 message. Bundle-pcde-example-at05a-X12-278.json
Lloyd McKenzie (Sep 10 2020 at 15:02):
CDEx Reference implementation presentation will be 1pm Eastern. Combined track touch-base will be at 4pm Eastern
Sreekanth Puram (Sep 10 2020 at 15:26):
May Terry said:
Sreekanth Puram said:
May, Do you have a sample patient bundle which contains the careplans, priorauthorizations etc that we can exchange between payers?
Sreekanth Puram - try this PCDE Bundle example which has an embedded EDI 278 message. Bundle-pcde-example-at05a-X12-278.json
will check that and update our system once.
Lloyd McKenzie (Sep 10 2020 at 15:41):
https://build.fhir.org/ig/HL7/davinci-ehrx/exchanging-request.html#task
Lloyd McKenzie (Sep 10 2020 at 15:55):
http://build.fhir.org/notification-full-resource.json.html
Lloyd McKenzie (Sep 10 2020 at 15:55):
http://build.fhir.org/subscription.html
Lloyd McKenzie (Sep 10 2020 at 15:59):
https://build.fhir.org/ig/HL7/fhir-subscription-backport-ig/
Lloyd McKenzie (Sep 10 2020 at 16:01):
Sreekanth Puram (Sep 10 2020 at 17:05):
@Rachel Goldstein and @Ron Urwongse We were able to test the endpoints provided. Looks good.
Sreekanth Puram (Sep 10 2020 at 17:06):
This is a good start
Rachel Goldstein (Sep 10 2020 at 17:06):
Sreekanth Puram said:
Rachel Goldstein and Ron Urwongse We were able to test the endpoints provided. Looks good.
that's great!
Sreekanth Puram (Sep 10 2020 at 17:07):
I will provide detailed. Feedback in the form provide after we are done with the Connectathon.
May Terry (Sep 10 2020 at 17:09):
FYI: per @Mark Scrimshire The PDex track will host the presentation at 3p on the payer endpoint directory followed by a payer-to-payer discussion. For those interested, tune in there at 3 and come back to this channel at 4p for the day wrap-up.
Sreekanth Puram (Sep 10 2020 at 17:09):
@May Terry and @Joe Minieri . It is taking a while add the data. I will try to give our endpoint by the end of the day
Rachel Goldstein (Sep 10 2020 at 17:29):
@Sreekanth Puram hope you can join the brief demo at 3pm ET breakout session too if you're able!
Sreekanth Puram (Sep 10 2020 at 17:54):
Rachel Goldstein said:
Sreekanth Puram hope you can join the brief demo at 3pm ET breakout session too if you're able!
Yes will do.
Sreekanth Puram (Sep 10 2020 at 19:02):
Sreekanth Puram said:
May Terry said:
Sreekanth Puram said:
May, Do you have a sample patient bundle which contains the careplans, priorauthorizations etc that we can exchange between payers?
Sreekanth Puram - try this PCDE Bundle example which has an embedded EDI 278 message. Bundle-pcde-example-at05a-X12-278.json
will check that and update our system once.
Hi May, We were going through the bundle. As per the spec each ActiveTreatement section should have a single treatment section but in the bundle there are multiple treatment sections under a single ActiveTreatement section.
May Terry (Sep 10 2020 at 19:25):
can you give a specific example? there are some "treatments" that are really a group. e.g.: disposable medical supplies might be grouped together with oxygen or a nebulizer.
May Terry (Sep 10 2020 at 19:59):
HRex/CDex/PCDE day wrap-up is beginning at 4p. @Sreekanth Puram - can you join?
May Terry (Sep 10 2020 at 20:09):
@Sreekanth Puram - @Lloyd McKenzie and I reviewed the example and yes, there seems to be multiple treatments under one ActiveTreatment. It is an error that was missed in validation and the profile likely needs an invariant in PCDEComposition added to check and enforce the composition structure. So... I'll fix the example and Lloyd is going to open a JIRA tracker.
Sreekanth Puram (Sep 10 2020 at 20:24):
Hi @May Terry Sorry, I just saw this message as I was in an other track. I was hoping to check on the Prior auth request(X12 interpretation piece).
Sreekanth Puram (Sep 10 2020 at 20:24):
Looks like you are done with the Track.
May Terry (Sep 10 2020 at 20:26):
@Sreekanth Puram - we're still on the track call and talking about CDex. Will you be around tomorrow morning to test your endpoint again with @Joe Minieri ? I should also have the modified PCDE example done late tonight/early tomorrow morning to send.
Lloyd McKenzie (Sep 10 2020 at 20:52):
Tracker created - FHIR#28478
Ron Urwongse (Sep 11 2020 at 12:07):
That's great Sreekanth. Any constructive feedback or questions?
May Terry (Sep 11 2020 at 14:37):
okay. @Sreekanth Puram and @Joe Minieri - attached is a modified version of the PCDE bundle which has one treatment per ActiveTreatment. Please review and let me know if it looks good. Thanks! Bundle-pcde-example-at05a-X12-278_fix.json
Sreekanth Puram (Sep 11 2020 at 14:51):
May Terry said:
okay. Sreekanth Puram and Joe Minieri - attached is a modified version of the PCDE bundle which has one treatment per ActiveTreatment. Please review and let me know if it looks good. Thanks! Bundle-pcde-example-at05a-X12-278_fix.json
Yes May. However we may need to wait till our Friday meeting to do that.
May Terry (Sep 11 2020 at 15:27):
@Sreekanth Puram - What time will you be available? Our Track Highlight is at 3p. We probably want to sync-up before then.
Sreekanth Puram said:
May Terry said:
okay. Sreekanth Puram and Joe Minieri - attached is a modified version of the PCDE bundle which has one treatment per ActiveTreatment. Please review and let me know if it looks good. Thanks! Bundle-pcde-example-at05a-X12-278_fix.json
Yes May. However we may need to wait till our Friday meeting to do that.
May Terry (Sep 11 2020 at 16:59):
Team recap and report-out prep at 1p today on the Whova Connectathon HRex/CDex/PCDE subsession.
Our Track Highlight session to all attendees will be today at 3p on the Whova Highlight Track subsession.
Lloyd McKenzie (Sep 11 2020 at 18:30):
Lloyd McKenzie (Sep 11 2020 at 21:07):
We'd been down to just Nicolai and I for about an hour and I'm not really anticipating any new joiners, so I've shut things down. Thanks everyone for their hard work. See you on our calls next week.
Sreekanth Puram (Sep 11 2020 at 21:33):
Hi May, sorry I was swamped with other tracks I was participating in. We can continue testing with over the week and have a demonstration this friday or the next
May Terry (Oct 28 2020 at 17:18):
Hi all! Just a quick reminder that we'll be using this channel to address any PCDE-related questions during the HL7 DaVinci Oct 2020 Implementation Track on 10/29 from 11-4p.
May Terry (Oct 29 2020 at 15:17):
Hi @Artem Sopin - following up on the PCDE client implementation. lmk what I can do to help support your testing.
Artem Sopin (Oct 29 2020 at 15:31):
@May Terry here is the poblem that we have (from email)
We have tried PCDe use cases with you and getting error back indicating that patient Lara Mirren is not found. As I remember we had an agreement that patient Lara Mirren would have an identifier with value 123456 on your end so you could do lookup by identifier. This identifier exists in our patient resource (see request_body.json)
"identifier": [
{
"use": "usual",
"type": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v2-0203",
"code": "MR",
"display": "Medical Record Number"
}
],
"text": "Medical Record Number"
},
"system": "http://hospital.davinciproject.org",
"value": "123456"
}
However, we are getting error “Unable to locate patient” (see response_body.json).
Could you please have a look?
May Terry (Oct 29 2020 at 15:38):
@Artem Sopin - for this October ImplementationAThon - the tracks don't have the HIMSS setup where there is one patient going through all the IGs in different sub-scenarios. For testing with PCDE at this event, it might make sense to create our example PCDE test patient in your system. Here's our patient details: https://davinci-pcde-ri.logicahealth.org/fhir/Patient/14
May Terry (Oct 29 2020 at 15:39):
From a messaging perspective, you'll need to first run the $member-match operation to retrieve the patient UMB. Here's an example of that. https://davinci-pcde-ri.logicahealth.org/fhir/Patient/$member-match
May Terry (Oct 29 2020 at 15:40):
Then after that, you'll need to create a PCDE TaskRequest to check if the Bundle is already available.
May Terry (Oct 29 2020 at 15:40):
The Task will return a Bundle id, which you then retrieve for the PCDE bundle.
May Terry (Oct 29 2020 at 15:41):
The Task resource replaces CommunicationRequest which was probably what Edifecs implemented back in the HIMSS20 prep days. The guidance on this is available in the PCDE CI IG build version: https://build.fhir.org/ig/HL7/davinci-pcde/artifacts.html
May Terry (Oct 29 2020 at 15:51):
We have a PCDE client reference implementation which has a _Tutorial_ page that includes the Patient information to use for $member-match: https://davinci-pcde-client.logicahealth.org/Tutorial. Use Patient 1 and include Old Member id as one of your search parameters because that's the one which has the bundle. The other 2 added were meant to demonstrate what might be returned if there were multiple matches resulting from insufficient search parameters in $member-match.
May Terry (Oct 29 2020 at 15:57):
@Artem Sopin - does your current client support this type of message exchange with $member-match and Task?
Artem Sopin (Oct 29 2020 at 15:59):
@May Terry we do not support (do not have implementation) for $member-match at this time. We also do not have Task in PCDe, we have only CommunicaitonRequest, Patient, Endpoint, Organization
May Terry (Oct 29 2020 at 16:02):
@Artem Sopin - that's unfortunate. Yeh, it's an absolute requirement to support $member-match and Task-based requests for PCDE and for CDex. It was introduced in the May 2020 FHIR Connectathon, and again in Sept 2020. Oh well. Not sure if you have time to refactor your code today, but if not, then happy to take this offline afterwards and schedule a time for testing your implementation when it's ready.
Artem Sopin (Oct 29 2020 at 16:03):
@May Terry yep, I see, it is a newer version of PCDe, we have not released updates for this version. We are on previous version published earlier and the one that was used during the last HIMSS
Artem Sopin (Oct 29 2020 at 16:04):
are you already updated to the newer version and discontinued the old one?
May Terry (Oct 29 2020 at 16:04):
yes. We left both methods for the May Connectathon, and then discontinued CommunicationRequest in the Sept 2020 Connectathon.
Artem Sopin (Dec 29 2020 at 19:10):
@May Terry send you a personal message, should have left it here probably.
May Terry (Dec 29 2020 at 19:28):
@Joe Minieri - looks like Edifecs has a PCDE sending and receiving app with Task and can be tested with our MITRE reference implementation. Can you work with @Artem Sopin on it?
Re-posting @Artem Sopin 's message requesting PCDE support for context:
Artem Sopin [said]:
I just wanted to update you that we have deployed the updated PCDE use case with Task resource and Communication Bundle. Could we connect and try it out with you? By the way, in PCDe there are two payers, let's say PayerA that submits a task to PayerB, PayerB prepares Communicaiton Bundle and updates Task to complete. So opiton1, we could act as a PayerA who submit a task to Mitre (Mitre becomes PayerB). Also, option 2, we could be PayerB who gets the Task from Mitre (Mitre becomes PayerA). Let me know if we could connect and which option we could use.
Artem Sopin (Dec 30 2020 at 01:24):
@Joe Minieri I have prepared the configuration instructions, I hope that might help to connect https://docs.google.com/document/d/149fyP8SZj3fCFM_jkJSgn7vYtCzVUD-g-qVtrFGt65k/edit?usp=sharing
May Terry (Dec 30 2020 at 16:14):
Hi @Artem Sopin - @Joe Minieri and I reviewed the document and are wondering if you're available this afternoon to meet offline and what time?
There is some content in there that needs some clarification since seems to still refer to our old implementation. If you're available, then we'll schedule a meeting offline and send the invite by email.
Artem Sopin said:
Joe Minieri I have prepared the configuration instructions, I hope that might help to connect https://docs.google.com/document/d/149fyP8SZj3fCFM_jkJSgn7vYtCzVUD-g-qVtrFGt65k/edit?usp=sharing
Artem Sopin (Dec 30 2020 at 17:01):
@May Terry yes please schedule a meeting with me, my email is in the google doc.
May Terry (Dec 30 2020 at 17:14):
@Artem Sopin - sent mtg invite for 2p et today via email.
Artem Sopin (Dec 30 2020 at 17:23):
@May Terry can you do 2:30 PM EST? I have a meeting at 10:30 AM PST (it is 1:30 PM EST) which overlaps with the one you have scheduled
May Terry (Jan 11 2021 at 23:48):
Here’s the agenda for the upcoming Jan 2021 FHIR Connectathon PCDE track: https://confluence.hl7.org/pages/viewpage.action?pageId=97459186#id-202101DaVinciHRex/CDex/PCDEHealthRecord,ClinicalData,&PayerCoverageDecisionExchange-Agenda
We’ll have the designated Connectathon track Zoom meeting up throughout the entire Connectathon so participants and observers can join at any time in case you need to test your implementations or ask questions about the IG or related topics. Interim communications can be made on this PCDE Zulip channel (https://chat.fhir.org/#narrow/stream/179207-connectathon-mgmt/topic/PCDE.20Track) for those whose time is split among multiple Connectathon tracks.
Joe, Lloyd, and I will be monitoring this Zulip channel between now and the Connectathon so feel free to reach out if you need support.
Last updated: Apr 12 2022 at 19:14 UTC
