Stream: committers
Topic: Profile based on a profile
Bryn Rhodes (Apr 21 2017 at 05:04):
I thought there was a topic on this already, but I can't find it. I know it's valid to define profiles as based on another profile, but when I try to do so in the IG using the spreadsheet's "Type" column, the StructureDefinition that is output still has the type and baseDefinition elements set to the underlying resource, not the profile I'm targeting. Is this supposed to work in the IG Publisher?
Grahame Grieve (Apr 21 2017 at 06:44):
yes it's supposed to work. Where is this?
Eric Haas (Apr 21 2017 at 07:58):
I've tried and doesn't work for me either. used to work with just{http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient} and I tried
Patient {http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient} too.
See here
Bryn Rhodes (Apr 21 2017 at 17:06):
Right, same behavior for me. This is in the QI Core IG, where we're trying to base the QI Core profiles on the corresponding US Core profiles.
Grahame Grieve (Apr 21 2017 at 20:48):
which profile should I look at?
Bryn Rhodes (Apr 21 2017 at 20:51):
Just committed the patient profile that I've been trying to get to work: https://github.com/cqframework/qi-core/blob/master/resources/patient-profile-spreadsheet.xml
Bryn Rhodes (Apr 21 2017 at 20:52):
It builds locally (we're not sure why it won't build remotely, but that's a different issue).
Grahame Grieve (Apr 21 2017 at 20:55):
won't build for me because you are using AdverseEvent.category which does not exist
Grahame Grieve (Apr 21 2017 at 21:01):
in fact, generally, the QICore Adverse Event profile is in deep disagreement with the FHIR Adverse Event
Bryn Rhodes (Apr 21 2017 at 21:03):
Well, it used to be a profile of Basic because there was no AdverseEvent resource, but we are working to align it.
Bryn Rhodes (Apr 21 2017 at 21:04):
But when I look at AdverseEvent it does have a category?
Bryn Rhodes (Apr 21 2017 at 21:04):
http://hl7.org/fhir/adverseevent.html
Grahame Grieve (Apr 21 2017 at 21:04):
so in the meantime, should you drop it from the ig, since it won't build?
Bryn Rhodes (Apr 21 2017 at 21:04):
It builds for me though :(
Grahame Grieve (Apr 21 2017 at 21:04):
but how? Are you using a very old IG publisher?
Bryn Rhodes (Apr 21 2017 at 21:05):
Ah, AdverseEvent doesn't have a category in the current build, but it does in 3.0.0.
Bryn Rhodes (Apr 21 2017 at 21:05):
We need to be based on 3.0.0 though.
Bryn Rhodes (Apr 21 2017 at 21:05):
Well, 3.0.1.
Bryn Rhodes (Apr 21 2017 at 21:06):
And the publisher we are using is from the downloads, but I'll copy a fresh one just to be certain.
Bryn Rhodes (Apr 21 2017 at 21:06):
Downloads from the 3.0.1, though, right?
Grahame Grieve (Apr 21 2017 at 21:07):
damn
Grahame Grieve (Apr 21 2017 at 21:07):
well, we're basically broken for now. I have to do about a days work to get sort this out
Grahame Grieve (Apr 21 2017 at 21:08):
I haven't separated the versions of build and STU3
Bryn Rhodes (Apr 21 2017 at 21:08):
Sorry :( Anything I can do to help?
Grahame Grieve (Apr 21 2017 at 21:08):
well, we can drop AdverseEvent from the IG until I sort that out - will try and do it over the weekend
Bryn Rhodes (Apr 21 2017 at 21:09):
Okay, I'll pull that out.
Bryn Rhodes (Apr 21 2017 at 21:45):
Removed AdverseEvent (and FamilyMemberHistory, started getting a differential snapshot error with the latest publisher jar?)
Grahame Grieve (Apr 21 2017 at 21:45):
ok. I'll investigate the profile on profile issue
Eric Haas (Apr 21 2017 at 22:46):
Meanwhile.... can look at mine See here
Last updated: Apr 12 2022 at 19:14 UTC
