Export

Select Export in the tabbed tool bar on the top of the screen. 

in order to export artifacts, you must first select the Implementation Guide(IG).

The Export page contains form fields that allow users to specify the details of their exports. Users can export the Implementation Guides (IGs) saved under the Browse/Edit tab at the top right side of the screen. Users can export IGs as bundles or HTML with the IG Publisher. Once the form fields are complete, select the Export button on the left side of the scrolling tab at the bottom of the screen.

  1. The "IG Publisher Package" generates a package using the published version of the IG to be used with the FHIR IG Publisher.  
    • Users can select either JSON or XML format for the output
    • The "FHIR IG Publisher JAR" can be included in the export package
    • The Export tool will take a few minutes to process. The length of time is correlated with the size of the export. 
    • After completing the process, the export will automatically download to users' computers in a compressed folder, and tthe user is prompted to download a ZIP package of all files necessary to execute the FHIR IG publisher.
    • When the IG Publisher is executed, the output from the IG Publisher is copied to a public location in Trifolia-on-FHIR for preview.  
    • HTML exports produce a package (ZIP file) for use with the FHIR IG Publisher. 
  1. The "Bundle" export format is a Bundle of all resources referenced by the selected implementation guide, including the implementation guide resource
    • Bundle exports produce a single download (pretty quickly) as a single XML file. This XML file is a FHIR Bundle that can be used to import the resources for the implementation guide in another FHIR environment.
    • Users can select the type of output, JSON or XML, the bundle will be exported in.
  1. The "GitHub" export format places all the resources within the IG into the specified GITHub repository/branch
    • Only resources that have a repository, branch and path will be exported to GitHub.  At least one resource must have GitHub location information specified to export
    • If the file already exists in GitHub, it will be completely overwritten by this export
    • When this tab is selected from the Export page, the user will be prompted to enter their GitHub credentials.   If the user does not log into GitHub initially, the "Login to GitHub" button can be selected before the export is commenced.
    • After a user has selected an Implementation Guide, the user must enter a commit message that will be associated with the IG on GitHub.