Stream: workflow
Topic: ExampleScenario
Grahame Grieve (Aug 05 2019 at 19:58):
GF#22855 - proposes allowing the example scenario to refer to non-FHIR content. The committee is receptive to the general idea, but we need to do some detailed analysis about this - how would you identify other content, and for other relevant content types, what do you need to say about them?
Lloyd McKenzie (Aug 05 2019 at 22:42):
@Jose Costa Teixeira This came from you, I believe?
Jose Costa Teixeira (Aug 06 2019 at 17:30):
I would not need to say much about them except a pointer and a location. Could be just a pointer like a filename, e.g. IFC_RASO17_190605112043298.hl7 or a URL for an iCalendar...
Grahame Grieve (Aug 06 2019 at 20:55):
a pointer and a location?
Jose Costa Teixeira (Aug 07 2019 at 15:25):
filename or url
Jose Costa Teixeira (Aug 07 2019 at 16:18):
Trying to think of a case: After a prescription medrequest/p1 for 15 days of treatment, the hospital realizes this will break their stock and after calculation and approval, issues the GS1 Order (xxxx.xml)
We _could_ use a binary for that, but the system will not issue a binary, it will deposit a file somewhere.
Grahame Grieve (Aug 08 2019 at 00:19):
I feel as though a lot more thought is required here. Will people really use example scenario in FHIR for this? Would IHE? (They’d be the biggest potential users?)
Jose Costa Teixeira (Aug 08 2019 at 05:41):
IHE would normally combine different standards, so I suggest yes (we must still decide, and likely a decision will come after a first trial/demo).
Not sure what is the alternative approach- is there any benefit in saying "as for an example scenario, we only support FHIR content exchange"?
Grahame Grieve (Aug 08 2019 at 05:43):
but if they're combining different standards - what IHE does, yes - would the use ExampleScenario for it? That's the bit that's hard for me to see. where would it help with an existing IHE spec?
Jose Costa Teixeira (Aug 08 2019 at 05:45):
not sure I understand the question. The benefit is to show the use case with concrete examples, which sometimes we put in text, sometimes we out in annexes. It is not normative content, if that is what you are asking.
Jose Costa Teixeira (Aug 08 2019 at 05:46):
The normative part for IHE Workflow conformance would not be example scenario, but another resource (we started looking at it some time ago)
Grahame Grieve (Aug 08 2019 at 05:55):
but example scenarios is not the concrete examples, which I follow the need for. ExampleScenario makes all the narrative around the examples computable... for a given low yield value of computable
Grahame Grieve (Aug 08 2019 at 05:55):
though I suppose now I'm picking apart the core purpose of example scenario...
Jose Costa Teixeira (Aug 08 2019 at 06:01):
what did I miss? The example scenario captures a concrete example of a set of actions, some of them including concrete instances of resources.
Jose Costa Teixeira (Aug 08 2019 at 06:03):
sorry if repeated, but this is an example of an example scenario (rendering prototype)
http://blog.zeora.net/mma/examplescenario-mma1-scenario.html
Jose Costa Teixeira (Sep 09 2019 at 09:26):
I just remembered why I required xslt 2.0 to incorporate plantUML in the rendering:
Plantuml can generate an svg, so I used the unparsed-text function to incorporate the sgv directly into the html.
Jose Costa Teixeira (Sep 09 2019 at 09:26):
i think that function (unparsed-text) is only available in xslt 2.0
Rik Smithies (Sep 09 2019 at 09:36):
But isn't the svg xml? Then you can just use the document() function.
Jose Costa Teixeira (Sep 09 2019 at 14:39):
ok. at the time i read it it seemed there was nothing in xslt 1.0. It is not unlikely i made a mistake. I will check, thanks
Last updated: Apr 12 2022 at 19:14 UTC
