search

HL7 / US-Core-STU3

This repository contains the US Core Implementation Guide is based on FHIR STU3 and defines the minimum conformance requirements for accessing patient data. For the Continuous Integration Build of the US Core Implementation Guide use the following link:
http://build.fhir.org/ig/HL7/US-Core
6 stars 9 forks source link

Prepublish punch list #13

Closed Healthedata1 closed 6 years ago

Healthedata1 commented 7 years ago
  1. remove flag icon -done
  2. make publisher US Realm SC -done
  3. Change Title /Font and add version = V1.0.0
  4. Update footer - think is done
  5. Update links to STU3 published root ( not build.fhir.org )
  6. Update the little yellow publish history
  7. create an archive list of version like this http://hl7.org/fhir/directory.html
  8. QA for typos grammar and content errors
  9. fix all qa.html errors ( check with GG on the cdcrec codesystem related errors )
Healthedata1 commented 7 years ago

Get instructions from GG and access to be able to do 7 above.

also see: (may not be done prior to publishing)

Line Items

12907 profile+spreadsheets+not+generating+complex+extensions+correctly (Eric Haas)
12910 *** is+publisber+not+working+when+create+a+dependency+on+CI+builds (Eric Haas)
12921 the+content+fragment+in+the+ig-publisher+is+duplicating+content+content (Eric Haas)
12922 Order+lists+by+name+not+id (Eric Haas)
12933 ig+publisher+creates+mapping+tab+has+column+for+profile+-but+is+empty (Eric Haas)

Healthedata1 commented 7 years ago

Prepublish punch list:

  1. make sure publisher, contacts and jurisdiction are all aligned in conformance resources

e.g.,

<publisher value="HL7 US Realm Steering Committee"/>
<contact>
  <telecom>
    <system value="url"/>
    <value value="http://www.healthit.gov"/>
  </telecom>
</contact>
<jurisdiction>
   <coding>
     <system value="urn:iso:std:iso:3166"/>
     <code value="US"/>
     <display value="United States"/>
   </coding>
 </jurisdiction>

  1. Update Title

    • Change title to reflect the published vs developmental version

    e.g., "US Core Implementation Guide CI Build" to "US Core Implementation Guide (Release 1)"

  2. Update the published version

    • Update the Title
    • Update footer
    • publish history - how to do this..
      1. create an archive list of version like this http://hl7.org/fhir/directory.html
    • note you can use the IG Business version specification you define in ig.json: "{{site.data.fhir.ig.version}} "

  3. Update path to the main FHIR specification published base ( not build.fhir.org )

    • use Jekyll site variable" {{site.data.fhir.path}}" ( or "{{ site.data.fhir.path }}" inside xml - the spaces matter for proper rendering) and define the the main FHIR specification in the ig.json configuration file "specification" : "[specification]" see IG Pub Documentation

    • if DSTU2 then update specification to http://hl7.org/fhir/DSTU2

    • if STU3 then update specification to http://hl7.org/fhir/STU3

  4. update links to the latest version of dependencies

    • use Jekyll site variable dependency url "{{site.data.fhir.[dependency-name]}}" or "{{ site.data.fhir.[dependency-name] }}" inside xml"

      e.g. “uscore” : Base url of a dependency implementation Guide (defined in ig.json) - "{{site.data.fhir.uscore}}" = http://hl7.org/fhir/us/core/stu1/

    again see see IG Pub Documentation for how these are defined in ig.json

  5. update any paths (links) in narrative sections to conformance resources using the Conformance resource variable:

    • for relative paths use "{{site.data.structuredefinitions.[id].path}}" or "{{ site.data.structuredefinitions.[id].path }}" inside xml.
    • for absolute paths use "{{site.data.fhir.canonical}}/{{site.data.structuredefinitions.[id].path}}" or "{{ site.data.fhir.canonical }}/{{ site.data.structuredefinitions.[id].path }}" inside xml.

  6. QA for typos grammar and content errors

  7. fix all qa.html errors

    • can view this at [canonical path to ig]/qa/html
    • lists bad links
    • errors and warnings for all conformance resources and examples

  8. push repo to GitHub - check for any rendering errors there

  9. Contact Publisher and coordinate with them