Confluence will be upgraded on October 20th, 2020 beginning at 6 AM EST. Estimated downtime is 2 hrs. Please email with any questions.
Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. test and make sure your local copy of the build process completes without errors (so that if something breaks, you can be confident it's your fault . . .)
  2. create the directory [name] in the source directory
  3. copy templates/template-spreadsheet.xml to [name]/[name]-spreadsheet.xml
    1. open it and replace "[ResourceOrDataTypeName]" in the first column of the Data Elements tab with [Name])
    2. select an appropriate w5 category (e.g. clinical.general) (see source/w5.ini for a list of categories)
  4. copy templates/template-notes.xml to [name]/[name]-notes.xml
  5. copy templates/template-introduction.xml to [name]/[name]-introduction.xml
  6. copy templates/template-example.xml [name]/[name]-example.xml
  7. add the new directory and its files to git
  8. edit fhir.ini
    1. add [name]=[Name] to the [resources] section
    2. add [name]=committee to workgroups section
    3. add [name]=0 to fmm section
    4. add a [name]=<securitycategory> to the security-categorization section, where <securitycategory>= <securitycategory>can be one of business, anonymous, patient, not-classified
    5. add [Name]=tla the tlas section
    6. add [name]=an entry in the security-categorization section of fhir.ini for the resource
  9. edit hierarchy.xml and add your page under the correct place within the site's navigation
  10. open compartments.xml with Excel and specify which search parameters can be used to place the resource in a Patient or Practitioner compartment (or leave empty if N/A)
  11. if your resource has an element named "status", open status-codes.xml with Excel and add the appropriate mappings to the status. Use other resources in the same category (definition, request, event) as a pattern for the mappings.
  12. add your resource to resourcelist.html and /resourceguide.html (both in the right category and under the right caption letter)
  13. add your resource as appropriate in source/administration-module.html, source/clinicalreasoning-module.html, source/clinicalsummary-module.html, source/conformance-module.html, source/diagnostics-module.html, source/financial-module.html, source/foundation-module.html, source/implsupport-module.html, source/medication-module.html, source/ontology-module.html, source/secpriv-module.html, source/terminology-module.html, and/or source/workflow-module.html
  14. add a translation for your resources name to implementations/translations.xml
  15. edit the example to fill out the [Name] on the base node and add a <id value="xxx"/> where xxx is what you're going to call the example (usually "example")
  16. test and make sure the build completes without errors
  17. commit all changes to a git branch, push to GitHub, and create a Pull Request (see]).