Stream: IG creation
Topic: Making a private template trusted
David Pyke (Jul 13 2020 at 18:29):
I am working on an IG for Carequality but the autobuilder won't use it because it's not "trusted". How do I instill trust in the template?
Jose Costa Teixeira (Jul 13 2020 at 18:34):
local template?
David Pyke (Jul 13 2020 at 18:49):
Yep, but when I push it to my git, which is hooked to the autobuilder, it says it's not a trusted template and won't run the scripts.
Lloyd McKenzie (Jul 13 2020 at 19:00):
You can't have any scripts in a 'local' template. HL7 will only auto-build against 'official' templates that we control the code for. (Because scripts in the auto-build environment could do nasty things both to our hosting environment as well as to the published HTML - which would then impact anyone who looked at it.)
Lloyd McKenzie (Jul 13 2020 at 19:00):
What are you trying to do with your scripts? Is it an HL7 IG or one for someone else?
David Pyke (Jul 13 2020 at 19:01):
It's for Carequality, I've used the generic template changed the colours and inserted a logo on top. Is there a way to just have that without creating the whole template?
Grahame Grieve (Jul 13 2020 at 19:02):
that shouldn't cause it to not be trusted. what file extensions does it contain?
David Pyke (Jul 13 2020 at 19:03):
It's a full copy of the generic template, I've put a couple images in and edited the project.css and the fragment-pagebegin.html
Lloyd McKenzie (Jul 13 2020 at 19:03):
Note that you can have a template that's based on another template
Lloyd McKenzie (Jul 13 2020 at 19:04):
That's what you should do here
Lloyd McKenzie (Jul 13 2020 at 19:04):
Take a look at the Da Vinci template for an example of how
David Pyke (Jul 13 2020 at 19:04):
okay, I'll have a look there.
Lloyd McKenzie (Jul 13 2020 at 19:06):
If this look and feel should apply to more than one IG, you should actually commit the template as a stand-alone template so that other IGs can reference it and the look & feel can be maintained in a single place.
David Pyke (Jul 13 2020 at 19:10):
Okay, then how do I do that. It'll be used for a few.
Lloyd McKenzie (Jul 13 2020 at 19:16):
We'll need to create a Git project and decide on an id. Is this for one of the accelerators?
David Pyke (Jul 13 2020 at 19:18):
Nope, just Carequality
David Pyke (Jul 13 2020 at 19:18):
I'll create a git repository and upload it.
Lloyd McKenzie (Jul 13 2020 at 19:18):
What's the rationale for a distinct look & feel?
Lloyd McKenzie (Jul 13 2020 at 19:19):
In general, we want the look & feel to be consistent for all HL7-published FHIR IGs
Lloyd McKenzie (Jul 13 2020 at 19:19):
We allow small differentiation for accelerators
David Pyke (Jul 13 2020 at 19:20):
It's not an HL7 published IG
David Pyke (Jul 13 2020 at 19:22):
Carequality has specific IGs for use between their implementers. I'm putting together the first one.
Lloyd McKenzie (Jul 13 2020 at 19:24):
Ah. Then, create your own Git project for your template (and set it up to use the CI build). Once it builds, your template should be available for use elsewhere and you can just reference it by id
David Pyke (Jul 13 2020 at 19:24):
Oh, okay great!
Jose Costa Teixeira (Jul 13 2020 at 19:30):
why creating a template if it's just for one IG?
Jose Costa Teixeira (Jul 13 2020 at 19:30):
ah sorry, nevermind. Several IGs
David Pyke (Jul 14 2020 at 14:29):
With Lloyd's help, I got it building but it's still not "trusted". What is the next step to get it anointed?
Lloyd McKenzie (Jul 14 2020 at 14:35):
No need to anoint - your custom template shouldn't copy the base template, just inherit from it
Last updated: Apr 12 2022 at 19:14 UTC
