Extension Viewer Update

I’ve posted an update to the Extension Viewer that I’ve been working on over the holidays.

The main changes are:

• It will display profiles as well as extensionDefinitions in a couple of formats – a direct JSON representation of the profile as well as a template based human representation. The latter doesn’t show the complete contents, but rather what are likely to be the most commonly used ones. That can change over time of course!
• The application tracks the number of times a profile/extensionDefinintion is viewed (total and unique)and displays that alongside the name in the various lists. It’s the start of the ‘social’ aspects of the app – I’ll put in more formal ‘likes’ later on
• The overall interface has been tidied up – for example you can ‘zoom’ the details of a profile/ExtensionDefinition to see more.
• I’ve also removed the XML representation for the moment as I need to use one of the specific FHIR parsers to do this properly

The next step will be to allow the app to access multiple registries. At the moment it only works on Grahames Server, and even then it’s got cached copies of the resources as they were a week ago – I’d like to be able to ‘subscribe’ to changes on the server and update the cache (and therefore the display) in near-real time (using the _since parameter that search offers), as well as being to access other servers.

Also implementing the ‘like’ is a high priority, and improving the search capability.

And the overall UI – especially how Profiles and ExtensionDefinitions are displayed – does need on-going attention. I’m sure that some data is not being correctly rendered in the Display…

I’m hoping to have this ready for the next connectathon – I’m not going to be there in person, but hope to participate remotely so will be good to be able to interact with others who are building DSTU-2 compliant servers. (Of course, to be accurate, at the moment we only have a candidate for DSTU-2 – it’ll be May/June before it’s passed – hopefully).

I’d also like to incorporate some of the ideas into the Clinical Connectathon app. Ideally, a user should be able to select an extension or a profile as the data entry form – but not sure how much of that will be done in time…

Do feel free to have a look and make any comments – remember, it’s just a prototype at present!