Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-41961

Packaging terminologies

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • Canonical Resource Management Infrastructure (FHIR)
    • 1.0.0-ballot [deprecated]
    • Clinical Decision Support
    • Packaging
    • Hide

      Agreed, explain that the intent of the Computable and Expanded ValueSet profiles is to support packaging terminologies for different contexts where a terminology server may or may not be available.

      Also address the concern about expansion size and how that would be handled in a packaging context.

      Show
      Agreed, explain that the intent of the Computable and Expanded ValueSet profiles is to support packaging terminologies for different contexts where a terminology server may or may not be available. Also address the concern about expansion size and how that would be handled in a packaging context.
    • Isaac Vetter/Chris Schuler: 10-0-0
    • Enhancement
    • Non-substantive

      13.2 - Consider providing guidance for how terminologies should be packaged. For example, should a ValueSet be pre-expanded? Or should only the definition of the ValueSet be included in the package, and terminology services later used to expand the ValueSets from the package. Or is there a general guidance on expanded size limits for ValueSets?

            Unassigned Unassigned
            seanmcilvenna Sean McIlvenna
            Sean McIlvenna
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: