Forcing Audit content requirements is not a good idea

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Highest
    • Situation Awareness for Novel Epidemic Response (FHIR)
    • current
    • Public Health
    • Profiles and Extensions
    • 6.1.1.1
    • Hide

      Simplify this to AuditEventBase, apply FHIR based codesets, but skip ATNA code sets except perhaps as example bindings.

      Show
      Simplify this to AuditEventBase, apply FHIR based codesets, but skip ATNA code sets except perhaps as example bindings.
    • Keith Boone/David Pyke: 29-0-1
    • Enhancement
    • Compatible, substantive

      Having specific requirements for AuditEvent content (specific codesystems and values) may step on internal organziaiton policy and technical requirements. I strongly advise that we remove the specific profiles for AuditEvent or, at minimum, reduce them to suggestions instead of hard requirements. I feel that having hard requirements for audit entries will have a long term negative effect on adoptions

            Assignee:
            Keith W. Boone
            Reporter:
            David Pyke
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: