Stream: Da Vinci
Topic: DEQM-R4
Eric Haas (Aug 16 2018 at 16:07):
@Bryn Rhodes @Lloyd McKenzie we will have two repros one for deqm and one for deqm-r4 artifacts which I have call 'deqm-r4 ' for now. deqm has several links that points to these artifacts.
DEQM and DEQM-R4 has links ( but only links) to each other and DEQM-R4 is really only has a single link back. I have several questions
- what should the repro name and package name be? ( repro: davinci-deqm-r4? package fhir.davinci.deqm.r4 ?)
- But how will the links resolve before and after publishing when Grahame does his magic. - I think this means they are they dependent on each other? In DEQM, I am referencing 3 different guides * 2 versions + 2 different versions of the spec = 8 different igs and specs using page level variables in the front-matter. I can manage that manually but I don't think grahame is going to be happy with that arrangement when if comes to publishing .
- I have no idea how this is going to work for the different published versions of DEQM - will need to create table. ( i.e., does the current version of DEQM reference the current version of DEQM-R4 ( yes) what about HEDIS and QICORE ( I think no))
Lloyd McKenzie (Aug 16 2018 at 16:08):
@Grahame Grieve will have to decide the expectations for npm name. Repo name doesn't really matter - For CRD I'm working to have it be a single repo.
Eric Haas (Aug 16 2018 at 16:09):
is that working with the autobuild
the R4 Spec is kind of a'slave' to the main spec
Eric Haas (Aug 16 2018 at 16:13):
DEQM is here BTW : http://build.fhir.org/ig/HL7/davinci-deqm/
Eric Haas (Aug 16 2018 at 16:15):
looks like Bryn has created a DEQM-R4 repro I'll import this to there soon: https://healthedata1.github.io/deqm-r4/
Lloyd McKenzie (Aug 16 2018 at 16:30):
Not yet. Working on that now
Lloyd McKenzie (Aug 16 2018 at 19:19):
@Grahame Grieve, is it reasonable for the base NPM to be hl7.fhir.us.davinci-crd and the R3 one to be hl7.fhir.us.davinci-crd.stu3?
Grahame Grieve (Aug 16 2018 at 22:37):
I'm not sure. I've just re-read the package spec a few times..
when implementers create a subset of the package, implementers are pre-approved to use the following suffixes: .terminology .conformance .[type]
Grahame Grieve (Aug 16 2018 at 22:37):
implies that .r3 sits in the type space but doesn't say so explicitly
Grahame Grieve (Aug 16 2018 at 22:37):
the choice for me is between hl7.fhir.us.davinci-crdr3 and hl7.fhir.us.davinci-crd.r3
Lloyd McKenzie (Aug 16 2018 at 23:01):
Why r3 and not stu3? The latter is the standard term for the release
Eric Haas (Aug 17 2018 at 03:58):
DEQM is opposite of Lloys deqm is R3 and deqm-r4 is R4
Lloyd McKenzie (Aug 17 2018 at 04:08):
One of these days we'll do something the same... ;)
Eric Haas (Aug 18 2018 at 07:58):
I have committed two IGs :
Eric Haas (Aug 18 2018 at 08:03):
| FHIR Version | Github location | npm-name | presumptive URL |
|---|---|---|---|
| STU3 | http://build.fhir.org/ig/HL7/davinci-deqm/ | hl7.fhir.davinci.deqm.stu3 | http://hl7.org/fhir/us/davinci-deqm-stu3 |
| R4 | http://build.fhir.org/ig/HL7/davinci-deqm-r4/ | hl7.fhir.davinci.deqm | http://hl7.org/fhir/us/davinci-deqm |
Eric Haas (Aug 18 2018 at 08:09):
right now they do not talk to each other :-( Well we were planning to ballot both but right now IMO should just ballot the STU3 version since its the stand alone version. to How do I get them to reference each other mainly to link from one to other?
Last updated: Apr 12 2022 at 19:14 UTC
