Stream: committers
Topic: CCDA IG
Rick Geimer (Aug 07 2016 at 13:23):
Grahame, can you please push the latest ccda2 guide to http://hl7.org/fhir/current/ccda/? It's not perfect yet, but much better that what's there currently, largely thanks to Sarah.
Grahame Grieve (Aug 07 2016 at 13:25):
ok
Grahame Grieve (Aug 07 2016 at 13:56):
posted
Grahame Grieve (Aug 07 2016 at 14:10):
what's the note about DSTU syntax and Simplifier about?
Grahame Grieve (Aug 07 2016 at 14:10):
how are you preparing the CCDA content?
Rick Geimer (Aug 08 2016 at 01:40):
@Graham,
Most of the Composition profiles were done using Trifolia, but one was done with Forge. Unfortunately it was an old version so many issues, even ignoring the DSTU 2 vs. STU 3 problem that we knew would be a manual fix since Forge does not support STU 3 yet.
Rick Geimer (Aug 08 2016 at 01:54):
I used Simplified to transform the old StructureDefinition syntax to current DSTU 2, now need to clean up remaining issues. This is all regaring the Transfer Summary composition profile.
Grahame Grieve (Aug 08 2016 at 10:56):
ok. The IG publisher should be able to load the Forge (DSTU2) structures directly
Sarah Gaunt (Aug 09 2016 at 06:17):
When I'm pointing to DAF profiles from the CCDA IG, should the reference be relative or absolute.
If relative what should it be?
If absolute, what should it be? Right now using "http://www.hl7.org/fhir/current/daf/" but not sure if that is correct...
Sarah Gaunt (Aug 09 2016 at 06:19):
Or does using "http://hl7.org/fhir/us/daf/StructureDefinition/daf-patient" get resolved to the correct place?
Grahame Grieve (Aug 09 2016 at 09:40):
last option is correct
Sarah Gaunt (Aug 09 2016 at 09:40):
Cool, thanks!
Rick Geimer (Aug 10 2016 at 13:53):
@Grahame Grieve Sarah kicked @$$ and got the ccda2 IG project down to zero errors. Please push to the public website. I don't want to touch it for fear of screwing up her awesomeneess :)
Grahame Grieve (Aug 10 2016 at 14:19):
ok sure I'll do that
Sarah Gaunt (Aug 10 2016 at 19:33):
There are links that don't work, now that the CCDA IG is up on the website. Things like
- http://hl7.org/fhir/ccda/StructureDefinition/ccda-us-realm-header-composition
- http://www.hl7.org/fhir/us/daf/daf-encounter.html
aren't resolving.... Is this something that will be fixed?
Rick Geimer (Aug 10 2016 at 19:35):
@Grahame Grieve Please check email. Would like to get the ccda2 IG posted to http://www.fhir.org/guides/registry so that ballotters have a way to find the IG. Sent you the wording you requested for doing so.
Grahame Grieve (Aug 10 2016 at 19:53):
thx\
Sarah Gaunt (Aug 11 2016 at 00:26):
So, I just found out that DAF has changed their resources to be "core" resources - so what was once daf-encounter is now daf-core-encounter. Is this something I can search and replace now and commit to the build, or is this something you can fix on your end? Or is it just too late?
Grahame Grieve (Aug 11 2016 at 00:27):
you can search and replace on this
Grahame Grieve (Aug 11 2016 at 00:27):
I'm not working on implementation guides yet
Grahame Grieve (Aug 11 2016 at 00:27):
and 1 1/2 hours left....
Sarah Gaunt (Aug 11 2016 at 00:27):
Ok, will fix on my end and commit...
PLENTY of time! HA!
Grahame Grieve (Aug 11 2016 at 00:33):
hah. I'm presently upgrading the FHIR version to 1.6.0. That's turned into a process that takes 4 hours (multiple builds, massive commits....)
Sarah Gaunt (Aug 11 2016 at 00:34):
Sounds awesome...
Sarah Gaunt (Aug 11 2016 at 00:38):
So just to double check - "http://www.hl7.org/fhir/us/daf/daf-core-allergyintolerance.html" is correct?
The links don't work right now as they are really here: "http://www.hl7.org/fhir/current/daf/daf-core-allergyintolerance.html"
Grahame Grieve (Aug 11 2016 at 00:45):
those links will work for ballot. I will make them work
Sarah Gaunt (Aug 11 2016 at 00:46):
Thank you
Grahame Grieve (Aug 11 2016 at 00:46):
ballot won't be in that location, but I can say where it actually is when I build it for ballot
Sarah Gaunt (Aug 11 2016 at 00:47):
Ok, sounds good
Sarah Gaunt (Aug 11 2016 at 00:57):
Commited the daf core update. Not making any more changes (unless I break the build, of course!).
Sarah Gaunt (Aug 11 2016 at 23:28):
So I'm still struggling to understand why I needed to map certain [type]/[id] profiles to a specific "base" eg:
"ValueSet/2.16.840.1.113883.1.11.20.22": {
"base": "ValueSet-2.16.840.1.113883.1.11.20.22.html"
}
The documentation states:
The file names of these generated pages will default to the following:
base: [ResourceType]-[id].html
and all I've done in the above JSON is explicitly state what the deafult base is ([ResourceType]-[id].html).
It seems like I'm repeating what is already set as the default for base.
I didn't do this mapping for the c-cda profile (US Realm Header) that most of the other profiles are derived from and have realised that the link included in the "This structure is derived from ..." doesn't work. This link is: http://hl7.org/fhir/ccda/StructureDefinition/ccda-us-realm-header-composition. The code used to grab this url is:
{{site.data.structuredefinitions[page.id].base}}
Maybe I should have used something else? The following looked to be my 3 options:
base : the url for structure definition from which it derives
basename : the name of the structure definition from which it derives
basepath : the url to the structure definition from which it derives
Or maybe I just need to explicitly map all the resources to what looks like the default base anyway to prevent problems?
Grahame Grieve (Aug 11 2016 at 23:38):
I'll have to debug it some time. You shouldn't have to map something to it's default value. Perhaps it got broken late in the process
Sarah Gaunt (Aug 11 2016 at 23:42):
Sounds good - will remind you in a few months when you've had time to recover!!
Eric Haas (Aug 12 2016 at 20:18):
When you state the base you aren't you explicity telling it to look in the pages folder for that page. If it not stated then you get the default build generated page of the same name. I am just speculating since in DAF we have custom pages for almost everything including valuesets so we always set the base value. Adding Valuesets to the IG was always challenging for me and it required adding and then removing stuff from the ig.file. I'd love to add how to video or screenshots to the publish doc but the valueset part is still a mystery.
Last updated: Apr 12 2022 at 19:14 UTC
