- DSTU2 Ballot to Final breaking changes
- DSTU2 Technical Correction 1 Tasks
- FHIR Management Group
- FHIR Product Director Page
- FHIR Product Director Position Description
- Governance Process
- Known Issues with the published FHIR Specifications
A final page you can populate content on.
HL7 FHIR CONNECTATHONS
The Centers for Medicare and Medicaid Services CMS will be hosting a Connectathon on January 7&8, 2020 at their headquarters.
The Da Vinci Project Connectathon will take place on December 11 & 12, 2019 at the Independence Blue Cross offices in Philadelphia, PA.
The HL7 International Conference in Australia will host FHIR Connectathon 23 on Feburary 2 & 3, 2020
Connectathon Planning Team
- Grahame Grieve, Health Intersections Pty Ltd
- David Hay, Orion Health
- Sandy Vance, HL7 Connectathon Administrator, AEGIS.net
- There are several FHIR tutorials scheduled through-out the week and a full list can be found by clicking the word "Tutorials" in the upper right corner of the Event Brochure which can be found here.
FHIR Proficiency Exam
- The FHIR proficiency test allows test takers to demonstrate their knowledge and understanding of the specification. This is a basic proficiency test, not a professional credentialing test. It will be multiple choice, multi-select, and true/false and based on the STU3 specification and not on field knowledge. Those who pass the test will receive the FHIR Proficiency Certificate, a Certificate of Knowledge.
- Tutorials on the FHIR Proficiency Exam can be found in HL7's Education on Demand site: https://www.pathlms.com/hl7.
- The exam can be taken either online or at one of 900 HOST centers of HL7's testing service Kryterion. More details can be found at http://www.hl7.org/implement/certification.cfm?ref=nav.
- FHIR Build Process
- FHIR IG PackageList doco
- FHIR IG QA process
- FHIR Implementation Guide Process Flow
- FHIR Implementation Guide Publishing Requirements
- FHIR Implementation Guides - Planned Balloting/Publishing
- FHIR Liquid Profile
- FHIR Package Cache
- FHIR Profile and IG Balloting
- FHIR Profile Authoring
- FHIR Spreadsheet Authoring
- FHIR Spreadsheet Profile Authoring
- FHIR Tools Registry
- Guide to Designing Resources
- IG Proposals
- IG Publisher Documentation
- Implementation Guide Parameters
- Managing Overlap Between Resources
- NPM Package Specification
- Process for Publishing a FHIR IG
- Profile Proposals
- Profile Tooling
- Resource Authoring
- Resource Considerations
- Resource Proposals
- Resource Types
- Chat.fhir.org Community Expectations
- Clinicians on FHIR
- Conformance QA Criteria
- Digital Signatures
- FHIR Code of Conduct
- FHIR Community Process
- FHIR Intellectual Property Rules
- FHIR Maturity Model
- FHIR Rules for Asking Questions
- Getting Involved
- IGs from other Organizations
- Implementer Support
- Interversion Compatibility
- Mailing List Instructions
- Migrating OIDs to FHIR
- Open Source Implementations
- Posting the FHIR specification on hl7.org
- Public FHIR Validation Services
- Public Test Servers
- R2-R3 Transformations
- R3-R4 Transformations
- Registering Code Systems
- Testing Platforms
- Using the FHIR Mapping Language
- Using the FHIR Validator
Location: Atlanta Marriott Marquis hotel (same as the HL7 Working Group Meeting occurring September 14-20)
Date of Training Workshops: September 11-13 2019
Training will occur 1-5pm on Wednesday and 9-5pm on Thursday and Friday
The FHIR Implementation Guide (IG) Workshop is for a series of three restricted, limited space workshops targeting IG publishers and new ballot reviewers. All attendees will be nominated in advance by the FHIR Core team.
The FHIR Core Team hasn’t identified a list of invitees yet, but if you’d like to suggest names to be included to the waiting list, just let us know and we’ll inform you when more details are available.
Entries below should select the appropriate workshops desired:
Workshop 1: Implementation Guide Creation (Wednesday afternoon and all day Thursday)
Workshop 2: Terminology considerations (Friday morning)
Workshop 3: Implementation Guide Ballot Review Best Practices (Friday afternoon)
- Indicates application email received by Wayne Kubick
Workshop 2: Terminology Considerations
|Workshop 3: |
IG Ballot Review Best Practices
|Linda Michaelson||Optumemail@example.com||X||X||Email from Linda (to Wayne Kubick): |
Yes, please put me on this list. I am copying in my Da Vinci team to promote me for the workshop – I am a co-lead on several workgroups and would like to be able to at least help in this process. From a scheduling perspective, when do you think it will be held? Linda
|Lisa Nelson*||MaxMDfirstname.lastname@example.org||X||X||X||Recommended by Wayne. Lisa has a candidate who is willing to learn and offer significant in kind contributions for creation and review.|
|Cheng Lui*||MaxMD||X||X||X||Recommended by Lisa|
|Benjamin Flessneremail@example.com||Recommended by Sean McIlvenna|
|George Dixon||AllScripts||X||Recommended by Sarah Gaunt|
|Emma Jones||AllScripts||X||Recommended by Sarah Gaunt|
|John Hatemfirstname.lastname@example.org||X||Recommended by Melva Peters|
|Andrew Statler||Cerner||Andrew.Statler@cerner.com||X||Recommended by Sean McIlvenna|
|Reuben Danielsemail@example.com||X||Recommended by Sarah Gaunt|
|Micheal Lawley||Michael.Lawley@csiro.au||X||Recommended by Sarah Gaunt|
|Smita Hastack||Samvit Solutionsfirstname.lastname@example.org||X||Recommended by Lloyd McKenzie|
|Robinette Renneremail@example.com||X||Recommended by Lloyd McKenzie|
|Rik Smithiesfirstname.lastname@example.org||X||X||Recommended by Lloyd McKenzie|
|Linda Michaelsen||Optumemail@example.com||X||X||Recommended by Bryn Rhodes (Duplicate of Row 1)|
|Patrick Werner||MOLIT Institutfirstname.lastname@example.org||X||X||X|
|José Costa Teixeiraemail@example.com||X||X||X|
|John Moehrkefirstname.lastname@example.org||X||X||X||Recommended by José|
|CDISC has a couple of people they'd like to send - need named individuals; and CDISC hasn't been participating in IG creation or ballot reviews.|
|Oliver Egger*||ahdis / hl7 swtzerland||(X)||X|
|Christine (Christi) Denney||Christi_d@lilly.com||X||X||X||Recommended by BR&R and Trisha Simpson. Author of 1 IG from BR&R for Sept 2019. Will be assisting with IG development for Research.|
|Craig Newman||Altarum||Craig.Newman@altarum.org||X||X||X||Is working on Reference implementations and would like to attend (Recommended by Dave Pyke)|
|Becky Angeles||Carradoraemail@example.com||X||X||X||Was the originator of the eLTSS project and would like to attend (Recommended by Dave Pyke)|
|Sheridan Cook||Gevityfirstname.lastname@example.org||X||X||X||Formerly w/ MiHIN, lots of experience doing IG-type work w/ v2, has now done v3 publisher work with FHIR (Recommended by Lloyd McKenzie)|
|Joee Garcia||Gevity||X||X||Developer/analyst who's been helping Lloyd with IG creation & review (Recommended by Lloyd McKenzie)|
|John Bender||ONCemail@example.com||X||X||X||Recommended by Matt Rahn and Wayne Kubick.|
|Paul Knapp||Knapp Consultingfirstname.lastname@example.org||X||X||Self-nominated|
|Jamie Parker||Caradorraemail@example.com||X||X||Recommended by Dave Pyke|
|Scott Gordon||FDA||Gideon.Gordon@fda.hhs.gov||X||X||X||Request to Wayne|
|Kathleen Connor*||VA/Book Zurman Inc.||firstname.lastname@example.org||x||x||x||Request sent to Wayne. Already have worked on FHIR build for FM/Security but need refresher on build especially for work on FHIR DS4P IG. starting in Sept. But may not need if 101. Wayne indicates that there's no space until Feb. Not going to AU. Maybe in May 2020 if needed.|
|Mark Kramer||MITREemail@example.com||x||x||Approved and confirmed by Wayne|
|May Terry||MITRE||mayT@mitre.org||x||x||Approved and confirmed by Wayne.|
The following checklist can be used as a template for performing an Implementation Guide review – it guides the overall process for the review.
This slide deck gives details for reviewing FHIR IGs: 2019-09 FHIR IG Review.pptx
To use this checklist, copy the content to a Word Document for each IG Review.
Step #1: Orientation / Conceptual
- Check stated Realm
- Check kind of IG – what expectations arise?
- Summarise what this IG does (is it clear from stated scope?)
- Check stated dependencies – if stated
- Check for missing appropriate dependencies
Step #2: Orientation / Technical
- Read note to balloters (if present)
- Check history notes
- Check qa.html
Step #3: Orientation / Approach
- Check kinds of exchanges
- Messaging (o Check messaging protocol)
- Make list of kinds of information exchanged
- Check consistent with realm core expectations
- Make list of actors described in system
- Characterise as Producer | Consumer | Repository
Step #4: Capability Statement
- Check resources exposed. For each resource
- Check Interactions
- Check Search Parameters
- Conformance expectations clear
- Check System Profile
- Check Use case Profiles
- Check Global Profiles
Step #5: Profiles
Check resources/profiles exposed. For each resource
- Check Text Summary – human to human
- Check Differential as summary (consistent with text summary?)
- Check what other related profiles exist in other IGs
- For each element in the differential:
- Check definitions – changed? Needs to be changed?
- Check any mappings added
- Check cardinality
- Check must support (and check it’s meaning is defined)
- Check Terminology Binding
- Any orphan profiles?
Step #6: Extensions
Any extensions? For each extension:
- Check context of use
- check related extensions
- For each element in the differential:
- (as above)
Step #7: Value Sets / Code Systems
- Check Copyright (externally sourced content)
- Check Versioning
- For code systems: something that needed to be defined?
Step #8: Specific Requirements
- For each:
- Defined / described?
- Requirements described?
- Do you agree?
- Error Handling
- Specifying correct behaviour for operational failures
- Mechanisms for handling erroneous data
- Audit / Provenance
- Consent / Privacy
- Test Cases / Conformance testing support
- Safety Issues (check)
Orphaned pages in this Confluence Space:
Log of work on migration of FHIR space
Joshua Procious added a comment - 2019-10-29 10:04
The reference to the FHIR Governance Board on this page: https://confluence.hl7.org/display/FHIR/Governance+Process is to the wiki as it hasn't been migrated to Confluence.
Joshua Procious added a comment - 2019-10-29 10:06
Two pages in the Confluence FHIR space "Connectathon 13" and "Connectathon 14" were deleted and NOT migrated due to them being included in the archive page listing "Previous Connectathons"
Joshua Procious added a comment - 2019-10-30 11:28 - edited
I have create the page FHIR Build Process as it was not in Confluence and seemed to be the primary link in multiple documents.
I created the page FHIR Profile Authoring and migrated from the referenced pages on the wiki.
I have created the page FHIR Profile and IG Balloting from the referenced pages on the wiki.
I have created the page FHIR Implementation Guide Authoring from the referenced pages on the wiki.
Joshua Procious added a comment - 2019-10-30 12:06 - edited
What is the guidance for how FHIR wants to handle the current Resource proposals on the WIKI?
Page on confluence here: https://confluence.hl7.org/display/FHIR/Resource+Proposals
Joshua Procious added a comment - 2019-10-30 03:51 - edited
Created page FHIR Package cache per requested migrated pages table: https://confluence.hl7.org/display/FHIR/FHIR+Package+Cache
Create page FHIR IG PackageList doco per requested migrated pages table: https://confluence.hl7.org/display/FHIR/FHIR+IG+PackageList+doco
Joshua Procious added a comment - 2019-10-31 09:53
FHIR Profile Considerations page on wiki is blank https://wiki.hl7.org/FHIR_Profile_Considerations
This link was intentionally left out of the FHIR Profile Proposal Template.
Joshua Procious added a comment - 2019-10-31 10:33
FHIR IG Proposal template was overwritten in the wiki with data so no instructions were present. https://wiki.hl7.org/Template:FHIR_IG_Proposal
The respective template in Confluence was populated with standard fields and general instructions but no guiding instructions per field.
Joshua Procious added a comment - 2019-10-31 01:03
I have create the IG Proposals and Profile Proposals pages in confluence.
Combined with the Resource proposals pages, they jointly use templates I've created in Confluence based on wiki templates.
Converting the blue text to cloaks in confluence and then listeners by label.
The bulk of the content for this page has yet to be migrated from http://wiki.hl7.org/index.php?title=FHIR