Stream: committers
Topic: Resource Status Codes
Grahame Grieve (May 31 2017 at 20:52):
Committers, one of the product goals for R4 is:
- Patterns: change the W5 framework to a pattern (logical model), tie the patterns to ontology, and use of patterns to drive more consistency (and how to do this without decreasing quality)
Grahame Grieve (May 31 2017 at 20:53):
my first step on this process is to
- define a formal code system for the cross-resource status codes
- improve the presentation of the status codes mapping table
Grahame Grieve (May 31 2017 at 20:53):
you can see this at http://build.fhir.org/sc.html
Grahame Grieve (May 31 2017 at 20:57):
as part of that I have highlighted some initial mappings that seem odd to me. Please look at this page, @Brian Postlethwaite, @Lloyd McKenzie, @Bryn Rhodes, @Cooper Thompson>
When looking at the page, see the highlighted issues, then look down the column for the identified codes, and review whether these are good mappings.
To help with the review, I have aligned the definitions of the mapped codes, along with draft definitions for the general codes, further down the page
Bryn Rhodes (Jun 01 2017 at 04:25):
The data-required status is used by GuidanceResponse, it's a status code indicating that not enough information was provided for the evaluation. Since we're deprecating GuidanceResponse though, this status will go away.
Grahame Grieve (Jun 01 2017 at 04:57):
I think it's mapping is probably wrong, but we won't worry about it if it's going to go away reasonably soon
Last updated: Apr 12 2022 at 19:14 UTC
