Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
FHIR Core (FHIR)
-
STU3
-
Patient Administration
-
Account
Encounter -
-
Brian Postlethwaite / Reinhard Egelkraut : 6-0-0
-
Enhancement
-
Compatible, substantive
-
R5
Description
During discussion of GF#18829, we opted to leave Procedure as an allowed reference from Encounter.diagnosis.condition, however we weren't really super comfortable with that.
The thing that we want to communicate is the ranking of diagnoses and procedures for the purpose of billing. I think this might make more sense to move into Account, rather than Encounter (this merits discussion though).
My tentative suggestion is to:
- Remove *Procedure *as an allowed reference from Encounter.diagnosis.
- Remove *Billing *from the Diagnosis Role valueset: http://build.fhir.org/valueset-diagnosis-role.html
- Add two backbone elements to Account: Acount.diagnosis *and *Account.procedures:
Account.diagnosis *0.. BackboneElement
condition Reference(Condition)
type CodeableConcept
rank positiveInt
Account.procedure *0.. BackboneElement
*procedure *Reference(Procedure)
- type* CodeableConcept
rank positiveInt
This moves the ranked procedure and diagnosis info into Account, which I think is where it belongs. It also makes the Encounter.diagnosis property very clearly only for diagnoses.
Attachments
Issue Links
- relates to
-
FHIR-28188 Claim and Encounter diagnosis and Encounter procedure should be harmonized
- Resolved - No Change
-
FHIR-16148 Encounter.reason and Encounter.diagnosis
- Published
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...