Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
    Tony Shannon
    welcome to PulseTile related discussions
    this channel can be used for questions etc related to the PulseTile UX framework
    if you need to share a screenshot here, try using this tool called Snaggy
    Hi, to what degree is PulseTile CUI compliant? Have you engaged with NHSD when creating it?
    Tony Shannon

    thanks @spencer-phil , the NHS CUI effort was certainly one of the influences behind this work.
    Aspects of PulseTile have certainly been crafted with CUI compliance in mind, eg Patient Banner.

    The time I spent at NHS CfH/NPfIT (inc connections to the CUI team there) led me to a few key conclusions
    1) there is a strong argument for a CUI in healthcare (just like renting a car and finding common usability patterns , you should find the usability of EHRs pretty consistent etc)
    2) publishing any UI standards as standalone standards will get you part of the way there, but you need an open source reference implementation of an open standard . CUI suffered from this gap imho , it had 1 Silverlight implementation that I can recall . Without that what you find in CUI is a range of good ideas from a UI perspective but nothing that shows how they could work together and so imho some of the components are somewhat overdone in parts and hard to work into an overarching UX/UI framework

    2) continued ... the same issue affected the update of the health design challenge work that came from the US
    Some excellent & beautiful UX design work but little/no implementations of any of them in action
    Tony Shannon
    3) so what is needed is a great UX/UI framework that combines a blend of open standards and open source
    In PulseTile we are offering a combination of both..
    As regards the standards space we are offering the UX framework and the principles behind it (eg 3 clicks from top to bottom)
    https://www.pulsetile.com/introduction-to-the-pulsetile-uxui-framework/ as a defacto international standard (until something better comes along) for an overarching healthcare UX framework, within which tiles/components (inc NHS CUI components ) could sit.. so we have the concept of a core framework and plugins.
    In addition we are offering it in at least 2 open source flavours .. React and AngularJS for now.. influenced by this thought-leading realworld.io work here https://github.com/gothinkster/realworld
    as regards NHSD engagement, this work is aimed internationally , ie not just for England/the NHS, but yes NHSD are aware , have been involved and have reused PulseTile for 2 recent projects, the GP Connect Demonstrator and more recently for GP IT Futures exploratory stuff.
    Hope that info helps , feel free to fire over more Q
    Tony Shannon
    PS) in reference to point 1 above, see section 7.4 User Interface (UI) and User Experience (UX) standards and frameworks in this recent related document here https://apperta.org/_attachment/DefiningOpenPlatform/Apperta_Defining_an_Open_Platform_April.pdf
    Thanks @tony-shannon , lots to digest there - appreciate your detailed response :)
    Hi, don't know if this is the correct place for this question but here goes... I am also involved in the StandIN project from Sweden that has been asking question over in the EtherCIS forum. Does PulseTile have support for building input forms from openEHR templates?
    Tony Shannon
    Hi @carrickg you are welcome to ask that Question here and will answer it happily. You will also get other ideas in the EtherCIS channel as Erik has done
    its worth understanding that we have been developing PulseTile & EtherCIS alongside QEWDjs, all info available from here;
    they have been developed to work independently , yet brought together in our open source "showcase".
    See playlist here to get a real breadth/depth of the stack;
    our interest is as much a great UX/UI as well as the world leading openEHR standard for data persistence
    so we believe the UX/UI should inform the data models as much as the data models should inform the UI
    so you'll see the overall framework and range of UX/UI Components in PulseTile here
    Tony Shannon
    the key thing to understand from a developer point of view is that we are seperating UI oriented JSON (PulseTile) from persistence oriented JSON (openEHR/EtherCIS) .. the reason for that is most healthcare applications should be able to handle data from external systems that are not openEHR compliant (FHIR) as well as those that are , which is where our middleware/integration layer QEWDjs comes in
    QEWDjs can be explained as very "JSON oriented", its nodeJS based tech etc. and one of its main jobs is the mapping between UI JSON and openEHR JSON with this kind of tooling here.
    If want to develop an app that natively handles openEHR JSON directly you dont need this... you can work directly from the openEHR JSON from EtherCIS
    but if you have any other JSON in the mix, then QEWDjs is set up for that
    One other thing, we have been experimenting with some tools that make the openEHR JSON to UI JSON even easier and see this prototype which is probably close to what you are looking for;