Stream: committers
Topic: status-codes.xml
Melva Peters (Oct 25 2016 at 18:03):
I'm trying to edit the status-codes.xml file but can not open it in Excel. Does anyone know how to fix this file so I can open it?
Eric Haas (Oct 25 2016 at 18:44):
look at the log file get the error and google it. usually finding the log file in windows is the hardest part.
Grahame Grieve (Oct 25 2016 at 19:06):
no log fail on mac. Mac users are not considered deserving
Eric Haas (Oct 25 2016 at 22:29):
it always works on my Mac even when it fails on Windows. So try a mac
Alexander Henket (Oct 26 2016 at 20:01):
Well I can reproduce on my Mac in both Excel 2011 and 2016. The DSTU2-last version opens normally.
Alexander Henket (Oct 26 2016 at 20:05):
The last version I can open is revision 9932. The revision 9961 after that is the first where it fails. Check in log "#9645 - rename Conformance to CapabilityStatement"
Alexander Henket (Oct 26 2016 at 20:16):
Found the problem and checked in a fixed version
Melva Peters (Oct 26 2016 at 20:17):
@Alexander Henket having the same issue with resource-spreadsheet.xml
Alexander Henket (Oct 26 2016 at 20:17):
Let's see if it is similar... hang on
Alexander Henket (Oct 26 2016 at 20:21):
Last working version was rev 7690.
Alexander Henket (Oct 26 2016 at 20:26):
Same thing. Grahame's version of Excel adds values in the settings for the window that the sheet is supposed to open in, that other versions of Excel do not like. After resetting the last working settings the sheet opens again. Weird Excel thing.
Solution for resources-spreadsheet.xml was to replace:
<WindowHeight>17610</WindowHeight>
<WindowWidth>-27136</WindowWidth>
with
<WindowHeight>15390</WindowHeight>
<WindowWidth>28800</WindowWidth>
Granted, a negative WindowWidth is unlikely, but other than that ... I don't know
Grahame Grieve (Oct 26 2016 at 20:36):
yay excel
Grahame Grieve (Oct 26 2016 at 20:36):
thx Alexander
Michelle (Moseman) Miller (Feb 18 2019 at 13:46):
Is it legal to have multiple codes mapped to the same canonical status? I see multiple examples of this in the status-codes.xml, but they aren't being honored. For example, Condition.verificationStatus has both unconfirmed and its child provisional mapped to unconfirmed, but the tooling generates the value set as if neither have canonical statuses mapped, per http://build.fhir.org/valueset-condition-ver-status.html. Is that a tooling issue or is it forbidden to map both to the same status?
Lloyd McKenzie (Feb 18 2019 at 15:55):
It's definitely possible to have 1..* maps and *..1 maps, so this sounds like a tooling issue.
Michelle (Moseman) Miller (Feb 18 2019 at 20:53):
GF#20402 created to investigate the tooling issue.
Grahame Grieve (Feb 19 2019 at 01:09):
ok I'll look at some stage
Last updated: Apr 12 2022 at 19:14 UTC
