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

Capabilities to validare identifiers in a NamingSystem

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Terminology Infrastructure
    • NamingSystem
    • Hide

      The attendees at the meeting feel this is something that a stand-alone application would provide (validating the format of an identifier). While interesting, your proposal does not fall within the scope of NamingSystem.  http://build.fhir.org/namingsystem.html#scope 

      Show
      The attendees at the meeting feel this is something that a stand-alone application would provide (validating the format of an identifier). While interesting, your proposal does not fall within the scope of NamingSystem.  http://build.fhir.org/namingsystem.html#scope  
    • Reuben Daniels/Rob Hausam: 5-0-0

    Description

      When saving or updating resources, one or several identifier values are often provided (Identifier.value) to universally identify the resource. At this point, it would be good to be able to validate that the identifier value that is provided is valid before saving it. 

      As identifier systems can be represented as NamingSystem resources, it would be good to have a simple operation to just validate an identifier value within that naming system (by provding the identifier value and identifier system). 

      Perhaps the NamingSystem resource could also be extended with elements for specifying validation rules. From my experience, the majority of business identifiers have some type of required format. 

      See this discussion in the FHIR chat:
      https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Validating.20business.20identifiers 

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            martingrundberg Martin Grundberg
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: