Print
Email
Business Case Development work stream
- Attila Farkas
-
- Away
- Posts: 127
7 years 3 weeks ago #2411
by Attila Farkas
Replied by Attila Farkas on topic Business Case Development work stream
Just a reminder that the Business Case workstream's weekly meeting is not scheduled for today but will reconvene next week. The main action item from our monthly call was to take the current work in progress content to early adopters of this technology, in this case MOHLTC. As an update, I would like to inform the team that we did meet with the project lead team at MOHLTC and they promised to review the work and contribute if applicable. We hope that feedback is received by next week's meeting and can be used to inform future work. Please remember that the space is open for contribution, review and comments on
InfoScribe
.
Please Log in or Create an account to join the conversation.
- Attila Farkas
-
- Away
- Posts: 127
7 years 1 month ago #2324
by Attila Farkas
Replied by Attila Farkas on topic Business Case Development work stream
For today's Business Case working group meeting please review the work in progress as a lot has changed since last week. The page can be accessed
here
.
Also as a way of reminder, the zoom meeting coordinates are in the News&Resources -> Events Calendar section of the site for your convenience are repeated here:
Weekly: Zoom calendar invite: zoom.us/meeting/325130317
Join from PC, Mac, Linux, iOS or Android: Join the call
Or iPhone one-tap (US Toll): +16465588656,325130317# or +14086380968,325130317#
Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 325 130 317
Also as a way of reminder, the zoom meeting coordinates are in the News&Resources -> Events Calendar section of the site for your convenience are repeated here:
Weekly: Zoom calendar invite: zoom.us/meeting/325130317
Join from PC, Mac, Linux, iOS or Android: Join the call
Or iPhone one-tap (US Toll): +16465588656,325130317# or +14086380968,325130317#
Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 325 130 317
Please Log in or Create an account to join the conversation.
- Grant Gillis
-
- Offline
- Posts: 1
7 years 1 month ago #2308
by Grant Gillis
Replied by Grant Gillis on topic Business Case Development work stream
Hi All
Enclosing draft text for your consideration a brief overview on FHIR (text below; Attila I will e-mail this in MS-Word file format. Might be too brief so happy to receive input/feedback on expansion in an either overall sense or in some particular areas as well. Can also add a few short statements to overview the entire business case (objectives, content) or a segue on to the next section.
Thanks kindly!
Bon weekend!
Best, Grant
Overview of FHIR
As healthcare delivery becomes more complex and increasingly digital, and as patients become more mobile, their personal health information needs to be more readily available to facilitate timely and quality diagnosis and care.
The health informatics community in Canada is actively working to support this availability through the use of FHIR (Fast Healthcare Interoperability Resources) so that health information is appropriately structured and standardized to facilitate its automated exchange and other related machine-based processing. So, what is FHIR?
FHIR is a rapidly emerging information standard informed by years of lessons around requirements, successes, challenges and lessons learned. FHIR describes data formats and elements (known as "resources") and an Application Programming Interface (API) for exchanging personal health information.
An open specification, FHIR has four principal elements:
1. A Comprehensive Data Model for defining personal health information and administrative data.
2. An API-Based Mechanism that simplifies the preparation and handling of information and data using ReST-ful (Representational State Transfer) protocols.
3. Open Source Tools to implement and test FHIR applications.
4. FHIR-Configured Servers that interact with the APIs to facilitate the information availability.
Through these four elements, FHIR aims to simplify and facilitate implementation without sacrificing information integrity. It leverages existing logical and theoretical models to provide a consistent, easy-to-implement yet rigorous mechanism for exchanging data between healthcare systems.
A further advantage of FHIR is that it can be used alone, but also in partnership with existing widely used standards. The FHIR specification is also in-line with the rapidly emerging mobile and web-based exchange of health information. Widely adopted, FHIR has the potential to reduce the risk, timeline and cost of developing the next generation of healthcare applications.
Enclosing draft text for your consideration a brief overview on FHIR (text below; Attila I will e-mail this in MS-Word file format. Might be too brief so happy to receive input/feedback on expansion in an either overall sense or in some particular areas as well. Can also add a few short statements to overview the entire business case (objectives, content) or a segue on to the next section.
Thanks kindly!
Bon weekend!
Best, Grant
Overview of FHIR
As healthcare delivery becomes more complex and increasingly digital, and as patients become more mobile, their personal health information needs to be more readily available to facilitate timely and quality diagnosis and care.
The health informatics community in Canada is actively working to support this availability through the use of FHIR (Fast Healthcare Interoperability Resources) so that health information is appropriately structured and standardized to facilitate its automated exchange and other related machine-based processing. So, what is FHIR?
FHIR is a rapidly emerging information standard informed by years of lessons around requirements, successes, challenges and lessons learned. FHIR describes data formats and elements (known as "resources") and an Application Programming Interface (API) for exchanging personal health information.
An open specification, FHIR has four principal elements:
1. A Comprehensive Data Model for defining personal health information and administrative data.
2. An API-Based Mechanism that simplifies the preparation and handling of information and data using ReST-ful (Representational State Transfer) protocols.
3. Open Source Tools to implement and test FHIR applications.
4. FHIR-Configured Servers that interact with the APIs to facilitate the information availability.
Through these four elements, FHIR aims to simplify and facilitate implementation without sacrificing information integrity. It leverages existing logical and theoretical models to provide a consistent, easy-to-implement yet rigorous mechanism for exchanging data between healthcare systems.
A further advantage of FHIR is that it can be used alone, but also in partnership with existing widely used standards. The FHIR specification is also in-line with the rapidly emerging mobile and web-based exchange of health information. Widely adopted, FHIR has the potential to reduce the risk, timeline and cost of developing the next generation of healthcare applications.
Please Log in or Create an account to join the conversation.
- Attila Farkas
-
- Away
- Posts: 127
7 years 1 month ago #2305
by Attila Farkas
Replied by Attila Farkas on topic Business Case Development work stream
Update following today's meeting for developing the FHIR Business Case. Participants: Grant G, Anne B, Shamil N., Yaron D., Igor S., Attila F., unnamed caller.
The group reviewed the approach articulated last week, discussed the first iteration of the Table of Contents and made assignments in fleshing out the content for most of the headlines. The space is publicly visible on InfoScribe , however, only a limited number of editorial licenses have been handed out. In case you have content to contribute, please contact me through this post and I can have your contributions reflected in the page.
In preparation for next week's meeting, please try to get content in early so that individual reviews can happen prior and we can proceed to evolving the space during the WG meeting. Thank you for contributing your time and know-how!
The group reviewed the approach articulated last week, discussed the first iteration of the Table of Contents and made assignments in fleshing out the content for most of the headlines. The space is publicly visible on InfoScribe , however, only a limited number of editorial licenses have been handed out. In case you have content to contribute, please contact me through this post and I can have your contributions reflected in the page.
In preparation for next week's meeting, please try to get content in early so that individual reviews can happen prior and we can proceed to evolving the space during the WG meeting. Thank you for contributing your time and know-how!
Please Log in or Create an account to join the conversation.
- Attila Farkas
-
- Away
- Posts: 127
7 years 1 month ago #2303
by Attila Farkas
Replied by Attila Farkas on topic Business Case Development work stream
Business Case meeting in progress. Join here: Join URL:
zoom.us/j/325130317
Please Log in or Create an account to join the conversation.
- Attila Farkas
-
- Away
- Posts: 127
7 years 1 month ago #2268
by Attila Farkas
Replied by Attila Farkas on topic Business Case Development work stream
From today's meeting:
- we have a general sense of scope and areas of interest that we would like to see covered in what we candidly call a business case
- to further flush out content, we will move the work to InfoScribe, a wiki like platform where we can start by sketching out the table of contents of the general brush strokes
- a number of editor accounts will be created for those participating on today's call (Gavin, Shamil, Igor, Finny, Joginder) and if others are interested in participating the editors can collect and represent their points of view
- the plan is to turn this work into a living space where relevant questions can be reflected and answered in an open forum of persistence benefiting various groups exposed to FHIR (i.e. architects, EHR implementers, middle layer users, POS vendors, etc.)
The link to the completed page will be posted here. Check back soon.
- we have a general sense of scope and areas of interest that we would like to see covered in what we candidly call a business case
- to further flush out content, we will move the work to InfoScribe, a wiki like platform where we can start by sketching out the table of contents of the general brush strokes
- a number of editor accounts will be created for those participating on today's call (Gavin, Shamil, Igor, Finny, Joginder) and if others are interested in participating the editors can collect and represent their points of view
- the plan is to turn this work into a living space where relevant questions can be reflected and answered in an open forum of persistence benefiting various groups exposed to FHIR (i.e. architects, EHR implementers, middle layer users, POS vendors, etc.)
The link to the completed page will be posted here. Check back soon.
Please Log in or Create an account to join the conversation.
Twitter