This wiki has undergone a migration to Confluence found Here
Difference between revisions of "June 13 - Work on the Clinical Maturity Model"
Jump to navigation
Jump to search
StephenChu (talk | contribs) |
StephenChu (talk | contribs) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | |||
+ | * Back to: [[Clinicians on FHIR - Sept 2017, San Diego]] | ||
+ | * Back to [[Clinician on FHIR 2017]] | ||
+ | |||
+ | <br> | ||
+ | |||
Attendees: Laura Heermann, Stephen Chu, Elaine Ayers, Joe Quinn, Kate Russell, Rob Hausem | Attendees: Laura Heermann, Stephen Chu, Elaine Ayers, Joe Quinn, Kate Russell, Rob Hausem | ||
Line 13: | Line 19: | ||
***- Conformance with this specification does not provide any guarantee of patient or data safety | ***- Conformance with this specification does not provide any guarantee of patient or data safety | ||
− | + | :::- Importance of clinical quality/appropriateness of FHIR design: | |
[[Image:Clinical-Appropriateness_2016-06-09.jpg]] | [[Image:Clinical-Appropriateness_2016-06-09.jpg]] | ||
− | + | <br> | |
+ | ::: - Questions: If it doesn't need to be clinically appropriate at design: | ||
+ | :::: # What mechanisms exist to ensur that "implementers can use it in a way that allows it to be used through clinically appropriate interfaces"? | ||
+ | :::: # Is clinical governance still relevant/required? | ||
+ | :::: # How can clinical confidence be ensured? | ||
<br> | <br> | ||
[[Media:FHIR_Clinical_Maturity_Criteria_201706132a.xlsx|FHIR Clinical Maturity Criteria 20170613.2]] | [[Media:FHIR_Clinical_Maturity_Criteria_201706132a.xlsx|FHIR Clinical Maturity Criteria 20170613.2]] |
Latest revision as of 20:58, 20 June 2017
- Back to: Clinicians on FHIR - Sept 2017, San Diego
- Back to Clinician on FHIR 2017
Attendees: Laura Heermann, Stephen Chu, Elaine Ayers, Joe Quinn, Kate Russell, Rob Hausem
Minutes:
- 1. Last weeks meeting looked at the exisiting maturity model and examined adding the clinical aspects to it
- 2. Discussion this week that we need to have our criteria, tight, concise and impactful.
- 3. The use case requirements
- a. Accurate in meeting clinical data capture
- Further notes taken in attached spreadsheet --- NOTE see the 2nd tab in the worksheet. 1st tab are older notes and thoughts on the topic.
- Noted references:
- http://www.hl7.org/fhir/conformance-rules.html
- - Conformance with this specification does not provide any guarantee of patient or data safety
- http://www.hl7.org/fhir/conformance-rules.html
- - Importance of clinical quality/appropriateness of FHIR design:
- - Questions: If it doesn't need to be clinically appropriate at design:
- # What mechanisms exist to ensur that "implementers can use it in a way that allows it to be used through clinically appropriate interfaces"?
- # Is clinical governance still relevant/required?
- # How can clinical confidence be ensured?
- - Questions: If it doesn't need to be clinically appropriate at design: