Loading...

XML

Word

Printable

JSON

Details

Type: Change Request
Resolution: Not Persuasive with Modification
Priority: Medium

Specification:

FHIR Core (FHIR)
Raised in Version:

DSTU2
Work Group:

Patient Administration
Outstanding Negatives:
STU
Related Artifact(s):

Encounter
Procedure
Resolution Description:

Hide

Both references are valid and important, however as noted by Lloyd, these should never be the same encounter/procedure referred.

An example use case would be a followup encounter to resolve complications from another encounter's procedure.

Clarifying text will be added to the specification.

Show
Both references are valid and important, however as noted by Lloyd, these should never be the same encounter/procedure referred. An example use case would be a followup encounter to resolve complications from another encounter's procedure. Clarifying text will be added to the specification.
Resolution Vote:
Andrew Torres/Iryna Roy: 7-0-0
Change Category:
Enhancement
Change Impact:
Non-substantive
Applied for Version:

DSTU2

Description

Resource references exist in both directions for Procedure and Encounter as follows:

Procedure.encounter (to Encounter)
Encounter.indication (to Procedure)

Per QA 5a:

Elements with a type of Resource Reference should be reviewed such that a given relationship shall only be represented in one resource, not both (and should generally be present on the resource that is normally created second - e.g. Procedure is usually created after Encounter, so reference would live on Procedure)

http://wiki.hl7.org/index.php?title=DSTU_QA_Guidelines

Attachments

Issue Links

is voted on by

BALLOT-2647 Negative - Michelle Miller : 2018-Sep-FHIR R1

Balloted

Activity

People

Assignee:: Unassigned

Reporter:: Michelle Miller

Watchers:: 1 Start watching this issue

Dates

Created:: 2016-09-09 09:56

Updated:: 2017-03-27 05:54

Resolved:: 2017-03-27 05:54

Vote Date:: 2016-09-21