2015May core #886 - US Core should define constrained data types

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • US Realm Task Force
    • DeviceMetric
    • Hide

      Not persuasive with mod - USRSC should establish a process to receive and approve US Realm profiles and to nominate certain profiles as US Realm Base Profiles which should be used as the starting point for US Realm FHIR artifacts to provide consistency where possible and reasonable within the US Realm.

      Show
      Not persuasive with mod - USRSC should establish a process to receive and approve US Realm profiles and to nominate certain profiles as US Realm Base Profiles which should be used as the starting point for US Realm FHIR artifacts to provide consistency where possible and reasonable within the US Realm.
    • Paul Knapp/Hans Buitendijk: 7-0-0
    • Enhancement
    • Non-substantive

      Comment:

      The US core should also include constrained data types (e.g. Patient.address), In the absence of such reusable components, implementation guides are constraining the same data types in separate and overlapping ways.

      Another option would be to create "constrainable" profiles for resources that require US localization in response to national regulatory requirements (e.g.MU, CQM).

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: