This wiki has undergone a migration to Confluence found Here
2016-05-26 Patient Care FHIR Call
Jump to navigation
Jump to search
Contents
Meeting Information
| Patient Care FHIR Resources Conference Call Location: Conference Call |
Date: 2016-05-26 Time: 5-6:30pm ET | ||
| Facilitator | Michelle M Miller | Note taker(s) | Michelle M Miller |
| Attendee | Name | Affiliation
| |
| Elaine Ayres | NIH/Department of Clinical Research Informatics | ||
| Stephen Chu | |||
| X | Eric Haas | Haas Consulting | |
| X | Rob Hausam | Hausam Consulting LLC | |
| Laura Heermann-Langford | Intermountain Healthcare | ||
| X | Emma Jones | Allscripts | |
| Russ Leftwich | InterSystems | ||
| Jay Lyle | Ockham Information Services LLC, VA | ||
| Sarah Maulden | VA | ||
| Jim McClay | Univ of Nebraska Medical Center | ||
| X | Russell McDonell | Telstra Health | |
| Lloyd McKenzie | Gevity (HL7 Canada) | ||
| Larry McKnight | Cerner | ||
| X | Michelle M Miller | Cerner | |
| Lisa Nelson | Life Over Time Solutions | ||
| X | Viet Nguyen | Lockheed Martin, Systems Made Simple | |
| M'Lynda Owens | Cognosante | ||
| Craig Parker | Intermountain Healthcare | ||
| Scott Robertson | Kaiser Permanente | ||
| Simon Sum | Academy of Nutrition and Dietetics | ||
| Iona Thraen | Dept of Veterans Affairs | ||
| Quorum Requirements Met: yes | |||
Agenda
Agenda Topics
- Agenda review
- Approve previous meeting minutes: 2016-05-05_Patient_Care_FHIR_Call
- Motion: Emma/Russell Abstain - 0, Negative - 0, Approve - 4
- Recap FMM and STU3 timeline
- Prior Action Item Follow-up
- QA
- gForge change request
Supporting Information
STU 3 Timeline
- Wed, June 1
- All resource and IG proposals for STU3 have been completed, reviewed by WG and submitted
- Connectathon tracks for Sept have been proposed
- Feedback on gForge submitted to FMG
- Sun, July 17 - Substantive content freeze for ballot -- core resources
- Sun, July 24 - Total content freeze, start of QA
- Wed, Aug 10 (midnight) - All QA changes applied
- Fri, Aug 12 - FHIR ballot opens
- Fri, Sept 12 - FHIR ballot closes
- Fri, Sept 16 - FHIR triage complete and ballot content loaded to gForge (or alternate)
- Sept 17-23 - Baltimore WGM
- Sun, Dec 11
- Reconciliation complete/substantive changes applied
- Just over 10 weeks
- Will re-evaluate at Baltimore based on volume of ballot comments
- Dec 31 - Publish
FHIR Maturity Levels
- Level 3 requires the artifact has been verified by the work group as meeting the DSTU_2_QA_guidelines and has been subject to a round of formal balloting; has at least 10 implementer comments recorded in the tracker drawn from at least 3 organizations resulting in at least one substantive change
- Substantive changes (element names, sort order, vocabulary bindings, etc.) need to be applied by ballot freeze (Aug 10).
- Unapplied QA checklist changes can be logged as ballot issues to be applied Sept-Dec. Substantive changes after ballot should be driven by ballot.
- Non-substantive changes are fine
- Level 2 requires artifact has been tested and successfully exchanged between at least three independently developed systems leveraging at least 80% of the core data elements using semi-realistic data and scenarios based on at least one of the declared scopes of the resource (e.g. at a connectathon). These interoperability results must have been reported to and accepted by the FMG.
| Resource |
Current FMM Level | Goal FMM Level | QA Status | QA Reviewer | Implementation | Comments |
| AllergyIntolerance | 1 | 3 | Rob | Argonaut | Need to complete changes for negation before we raise FMM | |
| Condition | 2 | 3 | PCWG | Argonaut | ||
| Procedure | 1 | 3 | Argonaut | |||
| CarePlan | 1 | 3 | Argonaut | |||
| Goal | 1 | 3 | ||||
| QuestionnaireResponse | 2 | 2 | Lloyd | Lloyd will QA to get to level 3 | ||
| Questionnaire | 0 | 2 | Lloyd | Lloyd will QA to get to level 3 | ||
| CareTeam | 0 | 2 | NA | NA | Aggressive goal (e.g. whether we'll get the implementations needed) | |
| FamilyMemberHistory | 1 | 2 | NA | NA | Aggressive goal (e.g. whether we'll get the implementations needed) | |
| ClinicalImpression | 0 | 1 | NA | NA | ||
| ReferralRequest | 1 | 1 | NA | NA | ||
| ProcedureRequest | 1 | 1 | NA | NA | ||
| Linkage | 0 | 1 | NA | NA | ||
| Flag | 1 | 1 | NA | NA | ||
| Communication | 1 | 1 | NA | NA | ||
| CommunicationRequest | 1 | 1 | NA | NA |
Note: Bold denotes top 20 resource based on survey
Note: Contraindication and Risk Assessment are owned by CDS, not Patient Care
Minutes
Negation Update
Prior Action Item Follow-up
N/A
QA
Talked about DSTU_2_QA_guidelines for Condition
- YES - 1a. Contexts identified
- Diagnosis, problem list, discharge summary problems
- NO - 1b. Resource differentiated from peers
- NO - 1c. Non-examples provided
- http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10090
- PCWG felt allergies can be documented as both Condition and AllergyIntolerance, just not *only* Condition; add boundaries for Condition/DetectedIssue
- NO - 2a. Examples cover all contexts & elements
- INFORMATION:Condition/identifier Path had no found values in any example. Consider reviewing the path
- INFORMATION:Condition/stage/assessment Path had no found values in any example. Consider reviewing the path
- When expand scope to include concerns, may need additional examples for concerns (e.g. fears, risks, barriers)
- Rename Example2 to Asthma on Problem List (or something to better represent the link back to the context)
- http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10090
- YES - 2b. Examples ok for clinical/business w/ comments
- YES - 2c. Extensions have valid/example URLs
- TBD - 3a. RIM mappings ok
- PCWG didn't review yet
- YES - 3b. External mappings provided
- RIM
- v2
- NO - 4a. Valuesets draw from right code systems
- CodeableConcept elements have one possible update needed
- Condition.code -- SNOMED (example, which is appropriate due to dx in ICD-10 vs problems in SNOMED)
- Condition.category -- FHIR defined value set (preferred)
- Condition.severity - SNOMED (preferred)
- Condition.stage.summary -- SNOMED (example)
- Condition.evidence.code -- SNOMED (example)
- Condition.bodySite -- SNOMED (example)
- code elements are OK
- Condition.clinicalStatus -- FHIR (preferred) -- doesn't include unknown, but minOccurs = 0
- Condition.verificationStatus -- FHIR (required) -- includes unknown, minOccurs = 1
- CodeableConcept elements have one possible update needed
- TBD - 4b. Value sets "representative" where possible
- PCWG didn't discuss whether the binding should be preferred instead of example
- Condition.stage.summary -- SNOMED (example)
- Condition.evidence.code -- SNOMED (example)
- Condition.bodySite -- SNOMED (example)
- PCWG didn't discuss whether the binding should be preferred instead of example
- YES - 4c. FHIR codes have good definitions
- YES - 4d. Code used for structural or FMG-cleared
- YES - 4e. Code types cover all scenarios, don't collide
- Condition.clinicalStatus -- FHIR (preferred) -- doesn't include unknown, but minOccurs = 0
- Condition.verificationStatus -- FHIR (required) -- includes unknown, minOccurs = 1
gForge Change Requests
N/A
Adjourn
Adjourned at 6:34 PM Eastern
Meeting Outcomes
Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.
