Loading...

XML

Word

Printable

JSON

Specification:

US Core (FHIR)
Raised in Version:

STU3
Work Group:

Patient Care
Related URL:
http://build.fhir.org/valueset-allergyintolerance-verification.html
Related Artifact(s):

AllergyIntolerance [deprecated]
Related Page(s):

Profiles and Extensions
Resolution Description:

Hide

Patient Care finds it non-persuasive since it doesn't change any clinical actions. The verificationStatus has cardinality of 0..1, so what use case needs to differentiate between not populated vs unknown? The same clinical due diligence will be done regardless of not populated vs unknown.

Show
Patient Care finds it non-persuasive since it doesn't change any clinical actions. The verificationStatus has cardinality of 0..1, so what use case needs to differentiate between not populated vs unknown? The same clinical due diligence will be done regardless of not populated vs unknown.
Resolution Vote:
Stephen / Rob: 6-0-0
Change Category:
Enhancement

Comment:

Retain verification status 'unknown.' Could argue that 'unconfirmed' is appropriate, but only during clinical workflow; not for transmission.

Summary:

Add verification status of 'unknown' to Allergy profile

is voted on by

BALLOT-7476 Affirmative - Greg Staudenmaier : 2019-Jan-FHIR US CORE R1