Stream: clinFHIR
Topic: Image upload problem
Ramya Reddy (Oct 12 2017 at 12:16):
1.In Scenario Builder Media resource image is not loading when I click the attachment link.It showing text only .
2.when I am giving the values of Media resource width,height and frames Data Type link is not working.
David Hay (Oct 13 2017 at 09:18):
Ah - those elements are datatypes not currently supported - I'll fix. wrt attachment, yes, I need to add a few more fields there also.
probably take a couple of days - I'll ping here when done...
Ramya Reddy (Oct 13 2017 at 09:22):
@David Hay Thanks for your reply
David Hay (Oct 13 2017 at 22:10):
OK - should be good to go. Take a try and tell me if there are any issues. (Note you can't enter in-line content at the moment. Not sure if that is desirable, and would only work for small attachments anyway..)
btw - when entering data there's a new option activated by a link 'toggle input mode' to the upper right of the screen when the 'Structure & Reference' pane is displayed. This shows the tree and the json of the resource side-by-side (hiding the navigator), which is more convenient when updating lots of elements.
bbtw - I'm working on a new input form which removes the modal input windows and will handle profiles much better. There's a preview on the 'experimental' tab of the launcher if you're interested (but be aware that anything entered in the new builder is not saved). Ultimately I intend to link it to the scenario builder as an option - as well as leaving it as a 'stand alone' resource builder...
Eric Haas (Oct 17 2017 at 19:18):
is there currently a way to referencing >1 resource type in the logical modeler. Can i edit the xml/json directly?
David Hay (Oct 17 2017 at 22:54):
per element? Sorry, no - I haven't done the UI for that. The output is an SD of course so you could modify it directly. I'm pretty sure that it will not remove existing multiple references - though it would pay to check...
Eric Haas (Oct 17 2017 at 22:55):
how do I get to the SD to modify it?
David Hay (Oct 17 2017 at 22:57):
The url (and id on the server) is in the model tab to the right. Make sure that you don't have the model open in the tool when editing it though! Let me know how you get on - I can update the UI if needed...
Eric Haas (Oct 17 2017 at 23:36):
The Scenario builder graph is so slick - can I publish them in my IGs? What attribution or cash do you need??
David Hay (Oct 18 2017 at 00:04):
Of course - go for it! (and let me know if there's anything I can do to make it better/easier...) attribution is always appreciated...
Eric Haas (Oct 18 2017 at 00:49):
I was able to modify the SD and upload easily. but the Scenario builder doesn't link to the resource if Patient links to the resource:
pasted image
Eric Haas (Oct 18 2017 at 00:50):
Is that because is a LM?
David Hay (Oct 18 2017 at 01:24):
sorry - don't quite follow. are you wanting to link from PHCase (? the logical model) to Condition and Observation? Whereabouts is the LM stored - I'll take a look... In theory, if the LM has an element of type reference then the SB should allow you to create the reference...
David Hay (Oct 18 2017 at 02:07):
Oh, hold on - is this a single element with multiple possible data types/references ? Again, in theory, this should work if the element is multiple in the model, but I suspect that the linking in SB won;t support that right now...
Eric Haas (Oct 18 2017 at 04:21):
both the Patient and Case Logical Model link to Observation and Condition and you have the option of creating this relationship in the SB menu using the "+" button, but the pretty graph doesn't draw the links like I did in the image above.
David Hay (Oct 18 2017 at 06:07):
I assume the LM is on a server somewhere? can you send me the URL & I'll take a look :)
Eric Haas (Oct 18 2017 at 14:47):
I saved the scenario as 'blah' in the SB
Eric Haas (Oct 18 2017 at 14:49):
here is the url : http://fhirtest.uhn.ca/baseDstu3/StructureDefinition/PH-Case
Eric Haas (Oct 18 2017 at 14:50):
it does produce an operation outcome error when loading but still seems to render so I ignored it....
David Hay (Oct 18 2017 at 17:20):
I think the issue is that the element name is 'reference' - the reference is being created, but the graph display routines get confused because 'reference' is the substring in the datatype that actually contains the reference to the resource (if that makes sense). Basically, if you change the element name to something else it ought to work. I did try to change it in the LM - but in the process mucked up your references (sorry) as it dropped the multiple ones when I tried to edit the name. However, if you edit it manually it ought to work (you may need to go back a version). Please let me know how you get on!
David Hay (Oct 18 2017 at 17:22):
I did get a couple of weird errors in the SB as well - it switched itself to readonly mode (I think as you were the author) and, as you say, there's an error loading the LM into the modeller. I'll look into those when I get a chance - but hopefully you are able to move forward with a bit of manual editing!
Eric Haas (Oct 18 2017 at 17:38):
great that is easy to change.
David Hay (Oct 18 2017 at 19:10):
good oh. Do let me know how it works out!
Eric Haas (Oct 18 2017 at 20:32):
Works like a charm thanks!
Eric Haas (Oct 18 2017 at 21:16):
it looks like the SB is pretty particular when your SD references a profile on a core resource it expects a profiled resource instead of a core resource. I think it should allow for core resources too since the graph is a high level view all you may want is the box at the vertices (nodes)
David Hay (Oct 19 2017 at 00:04):
So if your SD references, say, argonaut patient it should also allow a reference to a Core patient as well? I thought it did TBH - I'll look into that...
David Hay (Oct 19 2017 at 00:04):
glad the other issue worked out tho!
Eric Haas (Oct 19 2017 at 00:40):
It may be that I reference a Location profile that is unknown because that is where it would not all a core Location profile. I changed the LM to Reference(Location). which is an easy enough workaround
David Hay (Oct 19 2017 at 02:19):
glad that there is a work around, but not quite sure what (in an ideal world) you'd like to see happen - can you expand a bit?
Eric Haas (Oct 19 2017 at 13:59):
So if your SD references, say, argonaut patient it should also allow a reference to a Core patient as well? I thought it did TBH - I'll look into that...
that is what I'd like to happen and maybe it does and there was a problem with my sd...
Last updated: Apr 12 2022 at 19:14 UTC
