Stream: Da Vinci
Topic: DEQM Coordination
Bryn Rhodes (Feb 22 2019 at 01:25):
We're looking at starting to apply changes to the DEQM, both new content and applying reconciliation changes from last ballot. Should we use this DaVinci general stream to coordinate that, or is there a DEQM-specific stream that folks would prefer we use? @Eric Haas @Viet Nguyen
Eric Haas (Feb 22 2019 at 02:43):
Zulip is best. I have been out of the loop so I don't know where the new
content is documented but that is where we need to start...
Eric
Eric M Haas, DVM, MS
Health eData Inc
1183 Mountain View Circle, Napa, CA 94558
Rob Samples (Feb 26 2019 at 16:40):
Applying change to #17893
Rob Samples (Feb 26 2019 at 16:58):
Change applied
Rob Samples (Feb 26 2019 at 17:08):
Was unable to commit change
Matthew Tiller (Feb 26 2019 at 19:08):
Applying changes to #18638 https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=18638&start=0
Matthew Tiller (Feb 26 2019 at 19:09):
Also, I've forked the hl7 davinic project in order to use pull requests. There is an open pull request as of now, and I'll keep adding to it, but you can review as you have time
Eric Haas (Feb 26 2019 at 19:15):
I'd prefer to just commit directly and not fuss with PRs for now.... who is going to review the PR? its not that big an IG
Eric Haas (Feb 26 2019 at 19:16):
just remember to git pull frequently
Matthew Tiller (Feb 26 2019 at 19:17):
ok, that works for me. Eric, do you know who can add me to the HL7 github org? github id matthewtiller
Eric Haas (Feb 26 2019 at 19:18):
In fact I am adding some new infrastructure to it, and stubbing in the :
Colon Cancer Screening
Venous Thromboembolism Measures
use cases into the menu right now.
Eric Haas (Feb 26 2019 at 19:19):
Bryn I think is in charge of the git hub group. lemme see.
Eric Haas (Feb 26 2019 at 19:25):
@Grahame Grieve or @Lloyd McKenzie or @David Johnson can one of you add @Matthew Tiller to list of commiters to DEQM and DEQM R4?
Eric Haas (Feb 26 2019 at 19:28):
Actually on the call today, I misunderstood what @Rob Samples said. My apologies it is a good idea to say what we are working on in here. ( e.g. col page or xyq profile etc so avoid conflicts.)
Eric Haas (Feb 26 2019 at 19:34):
I usually tweak the stuff in the 'framework folder' to keep it updated with the latest bells and whistles. I have a few things to add like a copy button for some of the urls and few css tweaks but that is not a priority. let me know if you all are making changes in there so I can update my base template for other igs. There is also a handy _config.yml file in frameworks for site variables. In the future, I will be moving some of the frontmatter to there as well
Lloyd McKenzie (Feb 26 2019 at 19:52):
Right now, DEQM is only Bryn. Should I add anyone else?
Lloyd McKenzie (Feb 26 2019 at 19:54):
(@Matthew Tiller you should be good to go)
Matthew Tiller (Feb 26 2019 at 19:56):
thanks you
Rob Samples (Feb 26 2019 at 20:11):
@Lloyd McKenzie Can you add me as well? Rsamples
Matthew Tiller (Feb 27 2019 at 00:52):
@Lloyd McKenzie , I wasn't able to commit to the davinci repo. "remote: Permission to HL7/davinci-deqm.git denied to matthewtiller."
Lloyd McKenzie (Feb 27 2019 at 01:01):
@Matthew Tiller Git says it's waiting for you to respond to your invite - check your spam folder?
Lloyd McKenzie (Feb 27 2019 at 01:03):
Also, can you send me an email (lloyd@lmckenzie.com) confirming that you've read and agree to abide by Chapter 16 of the GOM and that you have signed up for and will actively monitor committers/announce?
Matthew Tiller (Feb 27 2019 at 02:22):
Thanks for pointing out the invites. I will send that email shortly
Eric Haas (Feb 27 2019 at 18:19):
adding new draft content to teh col page +index.html
Eric Haas (Feb 27 2019 at 18:41):
uploading diagrams to google sheets ( also pptx in source/pages/assets/images/source but google sheets lets you download as svgs ( and ppptx ) so working from there for edits.
google sheets lnk: https://docs.google.com/presentation/d/1srUEiA4eQHGA-xURFwUEcWmCN1q1LFJ3Wdy-dTgVqCE/edit?usp=sharing
Bryn Rhodes (Feb 27 2019 at 19:06):
I'm happy to add people to the DEQM-editors team, I just can't add anyone to the HL7 github organization directly.
Lloyd McKenzie (Feb 27 2019 at 19:13):
@Bryn Rhodes Just make sure everyone that you add has an email on file with me indicating their agreement to abide by Chapter 16 of the GOM and to monitor the committers/announce stream.
Eric Haas (Feb 27 2019 at 19:26):
looks like the DEQM resource graph diagram needs to be updated to include populations ...
Eric Haas (Feb 28 2019 at 00:10):
stubbed in col page, added summary measurereport profile (stub) and chagne measurereport to individual measurereport
Matthew Tiller (Mar 01 2019 at 15:55):
I'm editing the MRP workflow diagram. Will push changes today
Matthew Tiller (Mar 01 2019 at 22:15):
I'm confused about the section levels in the IG. I saw a commit that @Eric Haas made in Oct last year that increased the section level by one (added a '#') for all sections on several pages. In response to GF#17897 I was about to reduce it by one. But I can't figure out why the page titles are sectioned, but only on the build site. For example, https://build.fhir.org/ig/HL7/davinci-deqm/guidance.html has '2.1' as the title above the ToC. The 2018 Sep version of that page looks like I would expect http://hl7.org/fhir/us/davinci-deqm/2018Sep/STU3/guidance.html. I've looked at the CSS to no avail.
Eric Haas (Mar 01 2019 at 22:16):
The title in the front matter is ##
Eric Haas (Mar 01 2019 at 22:17):
The highest level in the markdown should be ###
Eric Haas (Mar 01 2019 at 22:17):
The section number are css
Eric Haas (Mar 01 2019 at 22:17):
The page need s to be added to igxml for this to work
Eric Haas (Mar 01 2019 at 22:18):
If you have trouble with this. Let me know is pretty easy for me to change this sort of thing
Bryn Rhodes (Mar 08 2019 at 14:19):
Okay @Eric Haas , I've got the last of the expected feedback plugged in to the home page on the quality measure IG. The content is HTML though, not markdown. Do you want me to send it as an email or just link to it here?
Bryn Rhodes (Mar 08 2019 at 18:03):
I committed those changes to the IG
Eric Haas (Mar 08 2019 at 18:09):
Ok
Eric Haas (Mar 08 2019 at 18:31):
Ideally as include files for the reused stuff?
Eric Haas (Mar 08 2019 at 18:52):
@Bryn Rhodes i think this content should replace the existing content before it. and not be appended to it. The how to read this guide should stay however.
Eric Haas (Mar 08 2019 at 18:52):
this is nice btw
Eric Haas (Mar 08 2019 at 18:55):
@Bryn Rhodes do you have an application that can generate examples. For COL. VTE? Otherwise I can create them but probably not before the tenth
Bryn Rhodes (Mar 08 2019 at 19:00):
Yes, working on that now
Eric Haas (Mar 08 2019 at 23:26):
ty !
Eric Haas (Mar 08 2019 at 23:26):
I will try the ref implementation for the MRP examples
Eric Haas (Mar 09 2019 at 00:55):
@Bryn Rhodes I tried to use the latest qi core package in ig.json for 3.1.0 and that doesn't work :-(
"dependencyList": [
{
"location": "http://hl7.org/fhir/us/qicore",
"name": "qicore",
"version": "3.1.0"
}
current is working do you know why?
Bryn Rhodes (Mar 09 2019 at 01:11):
Looks like the published package-list.json has a bug in it:
Bryn Rhodes (Mar 09 2019 at 01:11):
http://hl7.org/fhir/us/qicore/package-list.json
Bryn Rhodes (Mar 09 2019 at 01:12):
The 3.1.0 build is actually listed as 3.0.1
Bryn Rhodes (Mar 09 2019 at 01:13):
So you could try putting it in as 3.0.1, but there's no guarantee you'd get the right 3.0.1 I think.
Bryn Rhodes (Mar 09 2019 at 01:13):
There is a 3.2.0 about to be published, so I'd suggest sticking with current for now.
Eric Haas (Mar 09 2019 at 02:33):
OK thanks
Eric Haas (Mar 09 2019 at 02:47):
I have a tool to create the cap statements from a spreadsheet and create a pretty-ish narrative. I take a stab at it and then we can review ?
I assume there needs to be one for each actor for each set of interactions?
Bryn Rhodes (Mar 09 2019 at 17:26):
Yeah, that would be fantastic
Eric Haas (Mar 09 2019 at 18:34):
@Bryn is there a path to cqfm_r3?
The link 'StructureDefinition-cqfm-measure.html' for "CFQM Measure (STU3)" cannot be resolved
Bryn Rhodes (Mar 10 2019 at 02:01):
http://build.fhir.org/ig/cqframework/cqf-measures/StructureDefinition-measure-cqfm.html
Bryn Rhodes (Mar 10 2019 at 02:02):
And for Library: http://build.fhir.org/ig/cqframework/cqf-measures/StructureDefinition-library-cqfm.html
Eric Haas (Mar 12 2019 at 00:12):
ok 5 capstatements drafted for 5 actors: can you review?
1. Producer Server
2. Producer Client
3. Aggregator Server
4. Aggregator Client
5. Receiver Server
Eric Haas (Mar 12 2019 at 00:13):
next up is to add post interactions and then diagrams finish all diagrams that are not done yet.
Eric Haas (Mar 12 2019 at 18:01):
@Bryn STU and IG Version forDEQM?
Bryn Rhodes (Mar 12 2019 at 21:43):
STU 2, IG Version 2.0.0
Bryn Rhodes (Mar 12 2019 at 21:44):
@Eric, I just committed updates to the home page based on the discussions we had on the call earlier today.
Bryn Rhodes (Mar 12 2019 at 21:44):
I'm reviewing the cap statements, and there are a few things that I don't understand, but there are also some profile links that I think we need to switch to point to the CQF Measures IG instead of the DEQM profile (for Library and Measure)
Eric Haas (Mar 12 2019 at 23:01):
DEQM profile (for Library and Measure) exists in the guide, are we removing them as well? Happy to review capstatements on a call. whenever you are available
Eric Haas (Mar 13 2019 at 03:24):
for MRP examples, the https://ncqa.org/fhir/ig/Measure/measure-mrp is a bad link and getting an error. is there a new url?
Bryn Rhodes (Mar 13 2019 at 04:20):
That's the canonical, the link is: http://build.fhir.org/ig/cqframework/hedis-ig/Measure-measure-mrp.html
Bryn Rhodes (Mar 13 2019 at 04:20):
The CQL is here: http://build.fhir.org/ig/cqframework/hedis-ig/cql/stu3/mrp-logic.cql.html
Eric Haas (Mar 13 2019 at 05:17):
What gos in MeasureReport.measure? I thought it is the canonical url.
{
"resourceType": "MeasureReport",
"id": "datax-measurereport01",
"meta": {
"versionId": "1",
"lastUpdated": "2018-09-05T16:59:53.000+00:00",
"profile": [
"http://hl7.org/fhir/ig/davinci/StructureDefinition/datax-measurereport-deqm"
]
},
"status": "complete",
"_type": {
"extension": [
{
"url": "http://hl7.org/fhir/us/davinci-deqm/STU3/StructureDefinition/extension-dataCollectionType",
"valueBoolean": true
}
]
},
"measure": {
"reference": "https://ncqa.org/fhir/ig/Measure/measure-mrp"
},
"patient": {
"reference": "Patient/patient01"
Eric Haas (Mar 13 2019 at 15:55):
@Bryn Rhodes Shall I yank DEQM Library and Measure and replace with CQF ones?
Eric Haas (Mar 13 2019 at 15:57):
What is the dependency url for the CQF IG (or the package)
i.e. in ig.json i will need?
"dependencyList": [ { "version": "current", "name": "qicore", "location": "http://hl7.org/fhir/us/qicore" }, { "version": "2.0.0", "name": "uscore", "location": "http://hl7.org/fhir/us/core" }, { "version": "?", <--- "name": "cqf", <--- "location": "http://hl7.org/fhir/us/cqf???"<--- } ]
Bryn Rhodes (Mar 13 2019 at 15:58):
Yes, I just moved the cqf-measures ig into HL7, I'll let you know as soon as it's building there and get you links for the profiles...
Eric Haas (Mar 13 2019 at 15:58):
great and yes on yanking DEQM libarary and measure too?
Bryn Rhodes (Mar 13 2019 at 17:38):
Yes, I'll get the profile links as soon as I push to the new location
Eric Haas (Mar 13 2019 at 19:11):
Are the MeasureReport.measure urls all the same for for mrp data exchange, individual reporting and summary reporting?
Bryn Rhodes (Mar 13 2019 at 23:02):
Yes, for each use case.
Bryn Rhodes (Mar 14 2019 at 00:27):
Okay, library profile is here: http://build.fhir.org/ig/HL7/cqf-measures/StructureDefinition-library-cqfm.html
Bryn Rhodes (Mar 14 2019 at 00:27):
Measure profile is here: http://build.fhir.org/ig/HL7/cqf-measures/StructureDefinition-measure-cqfm.html
Eric Haas (Mar 14 2019 at 01:38):
TY : see my email for status on the qa errors all the links are a known issue for GG many of the errors will be fixed when add in the dependencies.. ig.json
Eric Haas (Mar 15 2019 at 03:02):
ok I replaced those resources , halfway through qa and changing actor names. pushed latest version.
Eric Haas (Mar 18 2019 at 16:08):
thanks for the examples.... I am not sure why the ci autobuild is failing is an NPE that I'm not getting locally. I have not committed yet after a pull. @Bryn Rhodes have you committed all your changes?
Bryn Rhodes (Mar 18 2019 at 16:16):
Everything's committed at this point. I'm not sure what the NPE is either, but there is at least one other IG getting the same thing.
Bryn Rhodes (Mar 18 2019 at 16:17):
There's one more error related to the hedis-practitioner, that's actually coming from the HEDIS IG, so I can fix that there, but I'm a little nervous about committing to the HEDIS IG right now with the issue with the auto-publisher...
Eric Haas (Mar 18 2019 at 16:19):
yes I just discovered the hedis practitioner too
Name Flags Card. Type Description & Constraintsdoco .. Task 0..* ... code S 1..1 CodeableConcept ... executionPeriod S 1..1 Period ... owner S 0..1 Reference(http://ncqa.org/fhir/us/hedis/StructureDefinition/hedis-practitioner) <------!!!!
Eric Haas (Mar 18 2019 at 16:20):
I have the package-list.json and a brief change-notes page to commit. I will investigate the NPE a little bit more
Eric Haas (Mar 18 2019 at 16:22):
I think we are in pretty good shape right now - there is one missing workflow diagram I will add in today
Eric Haas (Mar 19 2019 at 05:25):
@Bryn Rhodes IG is building again. all we need is the hedis practitioner. I have added the package-list.json and updated the title and version - can you check it out?
Bryn Rhodes (Mar 19 2019 at 06:21):
Fixed, looks really good!
Eric Haas (Mar 20 2019 at 16:33):
@Bryn Rhodes here is my dependency list for DEQM:
"dependencyList": [
{
"location": "http://hl7.org/fhir/us/qicore",
"name": "qicore",
"version": "current",
"package": "hl7.fhir.us.qicore"
},
{
"location": "http://hl7.org/fhir/us/core",
"name": "uscore",
"version": "2.0.0",
"package": "hl7.fhir.us.core"
},
{
"location": "http://ncqa.org/fhir/us/hedis",
"name": "ushedis",
"version": "dev",
"package": "ncqa.fhir.us.hedis"
}
],
confirming that is all good and nothing has changed....
Bryn Rhodes (Mar 20 2019 at 16:48):
Yes, that looks right to me.
Eric Haas (Mar 21 2019 at 20:05):
Hey @Bryn Rhodes can we update the roles in the connectathon to align with the DEQM IG?
Also I edited this in the IG and did not get a satisfactory answer:
"Not all data elements defined within the referenced CQM will always be present in the EHR for each patient for which an individual measure report is to be sent. Therefore, an individual measure report will not contain data for these data elements. For example, if a CQM has a criterion for “blue eyed patients” and the source system does not capture eye color, then the corresponding report for that patient will missing that observation.
Whereas individual measure reporting scenario defines this consistent approach to missing data, specifications of CQMs define the logical processing of missing data (e.g., how to classify a patient into various populations in the absence of an eye color observation). In other words, the CQM addresses how it factors in missing data when calculating criteria, and it is the job of the individual measure report to include relevant data that was present in the EHR, and to not include data that was missing from the EHR"
This suggests the measure definition defines what to do when the data is missing and not the profile...which makes sense because the measure author is going to have to deal with the missing data.
Bryn Rhodes (Mar 21 2019 at 20:19):
Yes, I'll update those. I struggled with the names when I put it together and chose EHR because Producer felt too abstract for a connectathon scenario, but I'll change it to Producer and provide some explanation.
Bryn Rhodes (Mar 21 2019 at 20:21):
Yes, that guidance is correct, putting it in the profile pushes the constraint down the stack closer to the producer. If it's not in the profile, then the measure author has to deal with the missing information in the measure specification.
Bryn Rhodes (Mar 21 2019 at 20:22):
So we put the constraints in the profiles so we could have the conversation. If it really is the case that the producers won't always be able to provide the data in that way, then either 1) In QI-Core we provide generalized guidance about how to deal with that, or 2) The measure authors deal with the variability in the measure specifications.
Eric Haas (Mar 23 2019 at 02:43):
@Bryn Rhodes @Floyd Eisenberg @Viet Nguyen The Ig publishing guidelines say "HL7 published implementation guides shall identify the ImplementationGuide.publisher as "HL7 International - <workgroup full name>" and ImplementationGuide.contact as the work group home page (i.e. http://www.hl7.org/Special/committees/[committee code])"
I have the publisher as Da Vinci with a link to the Da Vinci Project Page.. Who guide is this. Davinci or CQM's. ???
@Lloyd McKenzie What did you do?
Lloyd McKenzie (Mar 23 2019 at 03:16):
I specified FM as the work group and linked to their page - as they're the responsible work group. I did include a link to the Davinci home page on HL7 and to the public Confluence page on the home page of the IG.
Eric Haas (Mar 23 2019 at 04:52):
OK that is what I did.. I am upset that no one bothered to inform me of the DaVinci icon!
Lloyd McKenzie (Mar 23 2019 at 05:00):
Sorry. I saw that when I was looking at the website and figured I'd steal. :)
Eric Haas (Mar 23 2019 at 06:13):
I’ll add it during recon. ;-). I now understand all your comments about the footer. It was hard to get it all in one line.
Last updated: Apr 12 2022 at 19:14 UTC
