Jan 2015 Ballot Comment #216

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: High
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Health Standards Integration
    • AuditEvent
    • Hide

      add purposeOfEvent to event and participant, 0..*, Coding, "Purpose of the event. ", "use participant when you know that is specific to the participant, otherwise use event. (e.g. during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why)."

      eVote Motion to accept Agreed Change.

      From: owner-hsi@lists.hl7.org owner-hsi@lists.hl7.org On Behalf Of *Laura Heermann Langford
      *Sent:
      Wednesday, March 25, 2015 2:59 PM
      To: Laura Heermann Langford; hsi@lists.hl7.org
      Subject: Re: RESULTS on motion to accept disposition on block of FHIR CPs

      ?

      I have received the following votes:

      ?

      Aprove - 8

      Object - 0

      Abstain -0

      ?

      This represents a very high quorum for our votes on these FHIR CPs. ?With that I ?will close the voting and allow John M. to record the votes and keep moving on the work that needs to be done prior to the deadlines he is diligently working towards on the FHIR DSTU project plan.?

      ?

      ?Thank you everyone for your hard work with these CPs on a tight deadline.?

      ?

      Laura

      Show
      add purposeOfEvent to event and participant, 0..*, Coding, "Purpose of the event. ", "use participant when you know that is specific to the participant, otherwise use event. (e.g. during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why)." eVote Motion to accept Agreed Change. From: owner-hsi@lists.hl7.org owner-hsi@lists.hl7.org On Behalf Of *Laura Heermann Langford *Sent: Wednesday, March 25, 2015 2:59 PM To: Laura Heermann Langford; hsi@lists.hl7.org Subject: Re: RESULTS on motion to accept disposition on block of FHIR CPs ? I have received the following votes: ? Aprove - 8 Object - 0 Abstain -0 ? This represents a very high quorum for our votes on these FHIR CPs. ?With that I ?will close the voting and allow John M. to record the votes and keep moving on the work that needs to be done prior to the deadlines he is diligently working towards on the FHIR DSTU project plan.? ? ?Thank you everyone for your hard work with these CPs on a tight deadline.? ? Laura
    • Enhancement
    • Compatible, substantive
    • DSTU1 [deprecated]

      Comments
      3) Add reason (0..) to SecurityEvent.Event resource (to support Record Lifecycle Events without a corresponding Provenance resource)

      *Grahame's Comments

      So would the field only make sense in the absence of another resource? How can that make sense?

            Assignee:
            Unassigned
            Reporter:
            Gary Dickinson
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: