I am reliably informed that the session on Monday is going ahead as mentioned in the previous blog which is found here:
https://aushealthit.blogspot.com/2019/03/this-should-be-very-worthwhile-viewing.html
I am waiting for an e-mail regarding who and how interested parties can access the session.
It maybe worthwhile clicking the link about 15-20 mins before the session - say about 9:30 am on Monday 18/3/2019.
https://login.redbackconferencing.com.au/landers/page/3840b6
I will update this page if I learn more. Anyone else who knows feel free to tell us all via a comment!
David.
Update: As recently as 3pm 17/3/2019 the ADHA is tweeting the above link to access the session. I can only assume this is correct.
D.
2 comments:
No doubt the tweeting is a result of your posting David.
For the record the ADHA has from the outset has chosen to not simply ignore and exclude those with an interest and insights into making ehealth work better than it does currently. This placebo webinar is just a desperate attempt to present themselves as leaders. The fact the ignore the Australian a standard and previous IF publications is testament to their ignorance and arrogance. Anyway I will not attend because they did not extend an open invitation and it is obviously their twit account is a reaction to your action David.
For those attending I have listed some perspectives and feel free to put to the panel question based on these.
Some compounding factors:
Standards
•Conformity Assessment, Adoption, Business Change, Benefits Analysis
•Consensus agreements for process, information, and technical interworking
Conformity Assessment
•Connectathons and test suites
•Capability declaration and conformance recognition
Scale
•Organisational, Jurisdictional, National, International
•More complex cultures, policies, business models
Governance
•Distributed and multi-level on a national basis across solutions
Architecture
•Framework for aligned infrastructure and interfaces
•Act locally, think interoperably
Longevity
•Interoperability over time in spite of change
•Integration at a point in time
Maturity
•The practice of interoperability ... CMMI
•Internal focus to open standards, open interfaces, and open business
Some areas I think the panel will be able to cover and provide some direction of thought on:
Software vendors (even those not MSIA members)
Commitment - Openness, transparency, interworking as a business foundation
Architecture - Define architecture basis for product development
Standards - Identify standards as reference points for product function, information, and interfaces
Documentation - Describe all aspects of interworking assumptions for the product including clinical workflow, information, and technical perspectives
Interfaces- Expose Application Programming Interfaces (APIs) allowing information and behaviour use programmatically independent of any user interface
Software Procurement
Common Language - Define common concepts, patterns, and languages
Foundations - Identify foundational standards, precepts, models, and infrastructure
Architecture- Define overarching architecture
Connectivity and Capability Contract - Identify functions and interfaces for connecting systems
Procurement - Seek responses based on common language building on foundations within the required architecture delivering required connectivity and capability
Post a Comment