Skip to content

Need minimal profile for failed transactions #76

@ElliotSilver

Description

@ElliotSilver

Is your feature request related to a problem? Please describe.
While attempting to create an AuditEvent for a failed transaction, a team member tried to start with the profile for the successful operation and override elements in order to create a failed operation profile. Obviously this didn't work, as what they were attempting to do was not a further constraint. We realized that in order to provide guidance to our implementers on how to audit a failed event, we could not use any of the provided profiles, and would need to create profiles from scratch duplicating much of the content of the success profiles.

The existing text of "Note a failure AuditEvent may follow this pattern, but would not be a successful outcome and should have an OperationOutcome" present in many of the success profiles, while informative provides no assistance at a technical level. "Follow[ing] this pattern" requires starting from scratch since the success profile cannot be reused in any manner.

Describe the solution you'd like
There should be parallel failure profiles for each of the success profiles. Or, alternatively, a sufficiently generic failure profile to cover failure cases for each of the provided success profiles.

Describe alternatives you've considered
We could author our own failure profiles within our own IG, however IHE is in a better position to provide a common, validated approach.

Additional context
N/A.

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussionneeding committee discussionenhancementNew feature or requestquestionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions