Stream: fmg
Topic: survey tool
David Hay (Jun 04 2020 at 21:28):
Hi Guys - as discussed at the meeting yesterday, I've created a small tool to survey resource usage. Can you take a look at http://clinfhir.com/survey.html and let me know what you think? We can reset the data when we're ready after making any changes...
Results are listed in a tab on the page - but easy enough to create a csv download for importing into a spreadsheet... (or some other)...
John Moehrke (Jun 04 2020 at 21:33):
frustrating to have the resource I am interested at the bottom... see your checkbox which did work... making this better really requires two screens: one to select resources I am going to comment on, second screen the comments on those.
John Moehrke (Jun 04 2020 at 21:35):
could have three screens. first is checkboxes to those resources I am directly involved with development / prototyping, from that (second screen) (possibly a starting with the whole list or previous page?) those that I am aware are in production. notes on either page
John Moehrke (Jun 04 2020 at 21:35):
I would recommend "Dev / Test" be "Prototyping"?
David Hay (Jun 04 2020 at 22:02):
did you try the filter? Was trying to avoid multiple screens, but could certainly arrange in different ways...
David Hay (Jun 04 2020 at 22:02):
Could have a categorization display like in the spec...
Lloyd McKenzie (Jun 05 2020 at 04:49):
I'd just put radio buttons for dev/test vs. production and get rid of the checkbox. Would also be good to ask for organization name. Contact should be changed to 'email'. We don't really want phone numbers
David Hay (Jun 09 2020 at 21:25):
OK - updates at http://clinfhir.com/survey.html. If anyone can tell me where to find 'categorization' info - like here then I can add that...
John Moehrke (Jun 12 2020 at 14:59):
did we agree to allow an upload of a CapabilityStatement ? I know we agreed that they typically are not available in the constrained detail we want (either don't exist for clients, or are generic for servers). But if someone does have a well crafted Capability Statement it would be fantastic to see that as evidence too, and we would give that individual the benefit of not needing to fill out a form that they already have in a FHIR resource.
Lloyd McKenzie (Jun 12 2020 at 15:19):
We didn't. We could just invite them to email their CapabilityStatements to FMGContact@hl7.org
John Moehrke (Jun 12 2020 at 15:57):
sometimes it is hard to email xml.. but yes that could be explained as bonus-points
David Hay (Jun 12 2020 at 20:39):
I can add an upload...
John Moehrke (Jun 13 2020 at 12:46):
another easy response would be to have them list the IG they have implemented. again, if they have a CapabilityStatement it should (but likely donesn't) include these IG they support.. I really don't think we should take the current survey opportunity to get the IG, but eventually we should focus on IG rather than Resources.
David Hay (Jul 01 2020 at 18:43):
Latest version: https://survey.clinfhir.com/. (Still needs the list of resource types reviewed)...
David Hay (Oct 08 2020 at 18:33):
Have made the changes discussed yesterday. Specifically:
- 'product' is required. When a product is entered previous surveys for that product are shown in a separate tab. If the survey has been entered through the same browser, then there is a delete option. This seemed the simplest way to allow updates/corrections as well as a way of checking that no-one else has completed the survey for a given product.
- UI changes to the location of the filter options (by resource type or previously selected)
- any number of FHIR versions can be selected - and changed to "Lloyd order". The resources listed are derived from the selected versions.
- 'results so far' tab lists contactable numbers (where an email has been entered) - though not the actual emails of course
- if the call is HTTP, it will redirect to HTTPS
I didn't do the 'upload capability statement' option as mentioned in previous posts - but could look at that. Probably the easiest would be for the user to specify the root of the server, and have the app go fetch it. The server would need to support CORS of course, and the metadata endpoint unprotected...
IG's implemented is another interesting one. I'd suggest it's a different component of the survey rather than a way of finding supported resources. As @John Moehrke says, it would be elegant to get that from the capability statement, though you'd want a manual option as well. We'd also want to have a picklist for IG's - though I guess we'd also want to allow manual entry. Supported IG's may be of wider interest than supported resources too...
Comments welcome - and testing would be much appreciated! (It works for me :) ).
Last updated: Apr 12 2022 at 19:14 UTC
