Stream: terminology / utg
Topic: Publication Work
Grahame Grieve (May 23 2019 at 07:29):
@Ted Klein ok here: https://build.fhir.org/ig/HL7/UTG/
Grahame Grieve (May 23 2019 at 07:31):
let's start with: what pages do we need to add to this?
Ted Klein (May 23 2019 at 18:43):
This looks mighty sweet so far, Grahame. Ideally, I'd like to have tabs in each of the Code Systems and Value Sets pages for the groups of resources that we have in separate groups in Git now (and are read in by the local Vocab Tx Server: V2, V3, Unified, CDA, FHIR, and External (non-HL7). I need to write the text for the part above the links of course. We also need to figure out when if makes sense to move some of the FHIR stuff that was changed to terminology.hl7.org for R4 to the UTG Git as well (might need to add some extensions for the provenance tracking, not sure yet)
Grahame Grieve (May 24 2019 at 21:27):
do we really want to have tabs? THey're not my favourite thing.
Grahame Grieve (May 24 2019 at 21:29):
currently, the navigation bar across the top has
Home | Code Systems | ValueSets | Concept Maps | Naming Systems | Downloads
Wouldn't we be better to have
Home | v2 | V3 | CDA | FHIR | External | other
?
Lloyd McKenzie (May 24 2019 at 23:50):
Naming Systems aren't specific to any product family. ConceptMaps may well cross families. So I think the current navigation bar is correct
Lloyd McKenzie (May 24 2019 at 23:50):
Within ValueSets and CodeSystems, it's useful to be able to navigate by family, though there should also be an "everything" view.
Ted Klein (May 25 2019 at 14:07):
@Grahame Grieve What Lloyd said. :-). Agreed they are not the best, but the goal is to eventually have all the content be across all families; the process of unification of content will be to merge stuff that was developed independently and thus is different today, but has no business purpose for being different in general. This has already been done for a few items, like ObservationInterpretation. For now, each of the product families will have a manifest of the objects that are published as part of that family; note that the sets are not entirely disjoint, ie V2 published with the V2 Standard some V3 code systems and value sets, FHIR publishes some V2 and some V3, etc - CDA is the same. Many of the families use various "External" stuff, e.g. the CDC MVX and CVX, HSLOC, etc. What is why we have a manifest for the External as well. One of the very next things to do is to build the CDA manifest (once SD lets me know what actually should be in it), the overall full External manifest, and the FHIR manifest (for the FHIR objects that are to live in terminology.hl7.org
Ted Klein (May 25 2019 at 14:11):
@Grahame Grieve Also been thinking about what you said about the name; agreed. But there is benefit to having a short and sweet rolls-off-the-tongue name or acronym...I'm thinking right now (first random though in my cluttered head) "Unified HL7 Terminology" which could then be called UHT ("ooohtt". LOL). On top of that, I am assuming I need to write a LOT of the boilerplate text to head up the tabs on top, and also in the Home tab page. I am happy to begin doing that; let me know how and when and in what form I can supply the text to you. (I am thinking that the base text pages should be in Git also and IGPublisher can just suck them out, changes can just be posted, but maybe that is a bad idea...?)
Grahame Grieve (May 26 2019 at 05:44):
ok check https://build.fhir.org/ig/HL7/UTG/codesystems.html
Grahame Grieve (May 26 2019 at 05:44):
sorting is definitely something we need to discuss
Ted Klein (May 28 2019 at 15:32):
Yes we need to discuss sorting. Also, what about the boilerplate text?
Grahame Grieve (May 28 2019 at 20:34):
well, what pages do we think we need?
Grahame Grieve (May 28 2019 at 20:35):
- landing page: index + introductory information
- downloads page - all the different packages you might want
- background page - description of how things work
Grahame Grieve (May 28 2019 at 20:35):
?
Grahame Grieve (Jun 06 2019 at 10:12):
ok. if you add this extension to the list resource it will drive the creation of a subset package:
Grahame Grieve (Jun 06 2019 at 10:12):
<extension url="http://hl7.org/fhir/StructureDefinition/list-packageId">
<extension url="id">
<valueString value="hl7.fhir.terminology.v2"/>
</extension>
<extension url="name">
<valueString value="V2 subset of HL7 Terminology"/>
</extension>
</extension>
Grahame Grieve (Jun 17 2019 at 06:19):
so where are? I think I've done the infrastructural stuff, but now we need to do the actual editing?
Ted Klein (Jun 18 2019 at 19:13):
OK I understand that will support the subset stuff for IGpublisher (for the publish-control manifests in LIST resources)
Ted Klein (Jun 18 2019 at 19:14):
I also assume that for all the subset manifests that extension will be needed?
Ted Klein (Jun 18 2019 at 19:16):
We still need the separate tabs (all, v2, v3, and once we get the manifests implemented cad and FHIR) for value sets as well as the code systems. I would like to also use this capability to generate browsable page of a proposa iln flight, will need to discuss details with you. We are NOT going to reimplement Git obviously, I am working on how I think the workflow can come together with the pieces we have.
Ted Klein (Jun 18 2019 at 19:25):
I also want to begin putting together the "actual editing" by which I think you mean the text blobs for the generated pages, boilerplate for the tabs, etc. I have no idea what format it needs to be in or what process you need in order for me to begin creating it.
Grahame Grieve (Jun 18 2019 at 20:01):
well, it needs to either html or markdown
Grahame Grieve (Jun 18 2019 at 20:02):
probably the easiest process is if we figure out what pages we need, I create the stubs and navigation between them, and then you fill the pages out
Ted Klein (Jun 19 2019 at 15:17):
that absolutely works. Let me take a stab at identifying which places we need the pages, should not be difficult.
Grahame Grieve (Jun 19 2019 at 22:06):
ok
Last updated: Apr 12 2022 at 19:14 UTC
