Uploaded image for project: 'Other Specification Feedback'
  1. Other Specification Feedback
  2. OTHER-2122

Explain modularization and module management

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Considered for Future Use
    • Icon: Highest Highest
    • HL7 Logical Model: Standardized Terminology Knowledge Base (OTHER)
    • 1.0
    • Terminology Infrastructure
    • Informative
    • Chapter 2.2: Asset Curation Requirements
    • Hide

      Added to Chapter 2 “Requirements, Section 2.2 “Asset Curation Requirements”:Added to Chapter 2 “Requirements, Section 2.2 “Asset Curation Requirements”:

       “Modules are used to organize content for maintenance and publication purposes. Modules are the domain or organizational name of the larger asset within which the component is meaningful, such as code system or edition. Modularity for terminologies should follow a similar design to modularity in software engineering. Deciding what belongs in certain modules or extensions within certain terminologies is a difficult subject that is out of scope for this document, but having support for the ability to create modules, recognize redundancy, and merge or retire concepts are important requirements that must be supported.”

      Show
      Added to Chapter 2 “Requirements, Section 2.2 “Asset Curation Requirements”:Added to Chapter 2 “Requirements, Section 2.2 “Asset Curation Requirements”:  “Modules are used to organize content for maintenance and publication purposes. Modules are the domain or organizational name of the larger asset within which the component is meaningful, such as code system or edition. Modularity for terminologies should follow a similar design to modularity in software engineering. Deciding what belongs in certain modules or extensions within certain terminologies is a difficult subject that is out of scope for this document, but having support for the ability to create modules, recognize redundancy, and merge or retire concepts are important requirements that must be supported.”
    • Carol Macumber / Keith Campbell : 14 - 0 - 0

      The introduction of modules begs the question of how to divide the whole into parts, and then how to coordinate, deconflict, and reintegrate the parts. Should modules be aligned according to clinical disciplines? Domains of knowledge? Semantic types such as clinical finding, procedure, observable entity, and substance?

      Since term definitions can and will cut across module boundaries, what are the implications for versioning? How will redundancy prevented or managed?

            Unassigned Unassigned
            Mark_Kramer Mark Kramer
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: