Stream: implementers
Topic: Condition status
Jay Lyle (Feb 16 2018 at 21:12):
As discussed in NOLA, Condition.clinicalStatus seems semantically mixed. It has some ragged edges, and there are ongoing discussions about what really belongs in there, and what use cases it needs to support. These discussions are unlikely to be completed in the immediate future, but the ballot deadline is approaching.
One option is to relax the datatype from code to CodeableConcept. This way, future discussions could refine the values (if necessary) without affecting the schema.
Useful input:
1. do your systems support the property?
2. what are the values your system uses? (some already answered in gforge)
3. what are the use cases the values support? Is this a property that needs to support a state machine, and should be 'code', or is it more clinically open ended?
4. how much of a problem would a type change to CodeableConcept be?
Last updated: Apr 12 2022 at 19:14 UTC
