- DSTU2 Ballot to Final breaking changes
- DSTU2 Technical Correction 1 Tasks
- FHIR Management Group
- FHIR Product Director Page
- FHIR Product Director Position Description
- FHIR Trademark Policy
- Governance Process
- Known Issues with the published FHIR Specifications
HL7 FHIR CONNECTATHONS
The HL7 FHIR community is an open, welcoming community that respects all members.
The HL7 FHIR project is committed to providing a community that welcomes new members and provides a pathway to education about FHIR and full integration into the community.
Connectathons are a key part of our community engagement!
What is a Connectathon?
An HL7 FHIR Connectathon is an event that is centered on developing the HL7 FHIR Specification including resources, profiles and implementation guides. The purpose of a Connectathon is to prove that the specification is complete and facilitate FHIR implementation guide maturity.
The HL7 FHIR Connectathon Approach
The HL7 FHIR Community Vision is to enable Health Interoperability through the use of FHIR and use that to deliver improvements in healthcare provision throughout the world. HL7 FHIR Connectathon participants come together several times per year to work alongside vendor peers, healthcare providers and administrators, and the individuals and organizations that actually wrote the HL7 FHIR specification. Test tools like Touchstone.com and others are made available for developers to rapidly learn to implement the standard and validate their conformance to the specification and mature implementation guides. The HL7 FHIR Community Vision is highly reliant on the building a specification for healthcare APIs that is highly reusable. The fact that an implementation guide can be re-used at many deployments drives down the time and costs and drives up quality of health data for all.
FHIR Resources and implementation guides that are early in their maturity are more open for debate. When multiple stakeholders come together and find that their code does not interoperate, either one of them did not interpret the specification or IG correctly or it could mean that the FHIR documentation was not complete enough. Thus the FHIR specification is often improved during Connectathon and depends on transparency in the work that happens during these events.
What happens at Connectathon stays at Connectathon!
Connectathons are a safe place for everyone to fail forward. Connectathon testing with peer organizations is good for developers and for the HL7 FHIR standard. Connectathons offer developers a better place to fail than at a customer site. Customers expect to use products, not participate in debugging. By allowing product vendors to practice interoperability in a Connectathon setting, vendors can come to resolution and inform the specification evolution so that true interoperability can be enabled.
Out of Cycle HL7 FHIR Connectathon Criteria for Approval by the FHIR Management Group
Needs to be sponsored by HL7 International or an affiliate and approved by FMG.
Must submit names of the coordinator and technical lead for the Connectathon
Need to have at least one person familiar with FHIR
Persons should have participated in a prior Connectathon, having an implementation, etc.
Remains a judgment call from FMG for now
Identify what version of the spec on which they will draw
Need to assert if they have requirements for a frozen version of the spec and what other requirements they have
Describe the scenarios to execute
Comments from experience will be DSTU comments.
Participate as a Track Lead:
Anyone is welcome to submit a Track Proposal for an HL7 FHIR Connectathon. HL7 International hosts three main Connectathons annually typically held the weekend prior to the Working Group Meeting; however, the virtual format has slightly altered that pattern. Track Proposals are generally accepted from 12 weeks prior to 6 weeks prior to the Connectathon and are reviewed by the FHIR Management Group. To find the track proposal deadline and the associated track template, review and watch the Connectathon Event Page for the Track Proposal Template and specific event details including Track Lead Orientation.
To Get Started Review the following:
Join the Connectathon as a Participant to test the HL7 FHIR Specification or an Implementation Guide:
Interested in attending a Connectathon? Be sure to register prior to the event! Registration typically opens about 12 weeks prior to the event, and more information about registration and track participation is available on the specific Connectathon Event Page below:
- Resource Proposals
- Resource Types
- Resource Authoring
- FHIR Spreadsheet Authoring
- Guide to Designing Resources
- Managing Overlap Between Resources
- Resource Considerations
- FHIR Build Process
- HL7 Process for Publishing a FHIR IG
- FHIR Implementation Guide Process Flow
- IG Proposals
- Profile Proposals
- FHIR Profile and IG Balloting
- FHIR Implementation Guides - Planned Balloting/Publishing
- FHIR Implementation Guide Publishing Requirements
- HL7 QA process for FHIR IGs
- IG Templates
- Implementation Guide Parameters
- IG Publisher Documentation
- FHIR Liquid Profile
- FHIR IG PackageList doco
- NPM Package Specification
- FHIR Package Cache
- FHIR Profile Authoring
- FHIR Spreadsheet Profile Authoring
- FHIR Tooling Ecosystem
- FHIR Tools Registry
- Profile Tooling
- GIT Conflict Resolution Documentation
- SMART Web Messaging
- FHIR Package Registry User Documentation
- FHIR IG QA Monitoring
- FHIR Core FMM Support
- Process for Publishing a FHIR Implementation Guide (for non-HL7 IGs)
- tx.fhir.org Documentation
- Mitigating Breaking Changes
- Change Requests
- Chat.fhir.org Community Expectations
- Clinicians on FHIR
- Conformance QA Criteria
- Digital Signatures
- Endpoint directory implementations
- FHIR Cheatsheets
- 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
- SMART on FHIR server implementations
- 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
- Is the purpose of the IG clearly explained?
- Have roles and use cases been defined?
- Does the IG have the appropriate dependencies? Is it reinventing existing content?
- Do the artifacts fit appropriately into the defined scope?
- Check stated Realm
- Check kind of IG – what expectations arise?
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
- Characterize 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 - elements should be 0..0 only if the inclusion of that element would be an error
- Check must support (and check it’s meaning is defined)
- Check Terminology Binding – extensible and preferred binding pose challenges for searching
- For each sliced element (including extensions), assure the generic short and definition have been replaced with real definitions
- Any orphan profiles?
Step #6: Extensions
Any extensions? For each extension:
- Is there a standard extension that could be used?
- Has the context of use been set (associating the extension with the type of resource it can be used with)
- If a simple extension, has the data type of the value been appropriately constrained? Has the extension's extension been set to 0..0?
- Has the short and definition of the extension been set? (These are appear in the profile, so they are important)
Step #7: Value Sets / Code Systems
- Check Copyright (externally sourced content)
- Check Versioning
- For code systems: something that needed to be defined?
Step #8: Examples
- Check that all examples validate against profiles
- Check that examples have all information required for the use case
- Where there are slices, examples should populate every slice. Check that the QA report to see if the slices were uniquely distinguishable.
Step #9: 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.
|Editing the Core FHIR specification with the Forge graphical data modeling user interface||Ward Weistra||Jan 28, 2021|
|Space||Section||Page||Location in New Space||Needs Review (Y/N)||Recommendations from Initial Review|
Reviewed with FMG
|Review comments from FMG||Status of changes||FMG Member(s) to help with review and update||Review Notes|
|2021-09-15||WIKI||https://wiki.hl7.org/FHIR_DSTU_monitoring||N||Was not moved over from wiki, however seems to be completely outdated.|
|2021-09-15||WIKI||https://wiki.hl7.org/FHIR_Ballot_Prep||N||Was not moved over from wiki, but page is only a link to the HL7 confluence calendar page.|
|2021-09-15||WIKI||https://wiki.hl7.org/SDC_FHIR_Document_Profiles||N||Was not moved over from wiki but is essentially a blank page|
|2021-09-15||WIKI||https://wiki.hl7.org/FHIR_Methodology_Process||Y||Was not moved over from wiki. Unsure if content is current|
|2021-09-15||WIKI||https://wiki.hl7.org/FHIR_Repository_Process||Y||Has links to project information from the FHIR Repository Process Project. Unsure if needed on confluence|
|2021-09-15||WIKI||https://wiki.hl7.org/FHIR_Design_Patterns||Y||Seems to be out of date. Mostly asking questions for things that appear to have been answered already.|
|2021-09-15||WIKI||https://wiki.hl7.org/FHIR_for_Consumers||Y||Unsure whether this should be brought over/updated or not|
|2021-09-15||WIKI||https://wiki.hl7.org/FHIR_for_Clinical_Research||Y||Unsure whether this should be brought over/updated or not|
|2021-09-15||WIKI||https://wiki.hl7.org/Organizations_interested_in_FHIR||Y||Does not appear to be represented in confluence. If it is not, recommend adding it|
|2021-09-15||Confluence||Administration||Known Issues with the published FHIR Specifications||Y||Seems unnecessary with JIRA. Recommend removal.|
|2021-09-15||Confluence||Administration||Governance Process||Y||Outdated information. Either needs update or removal|
|2021-09-15||Confluence||Administration||FHIR Trademark Policy||Quick Links||Y||Should be reviewed to make sure information is current. I believe it is.|
|2021-09-15||Confluence||Administration||FHIR Product Director Page||Governance||Y||Assuming this is the only place to find this information, it might need an update from Grahame but otherwise is fine.|
|2021-09-15||Confluence||Administration||FHIR Product Director Position Description||Y||With the above page, this seems redundant. Additionally, it reads more like a job posting.|
|2021-09-15||Confluence||Administration||FHIR Management Group||Governance - Committees||Y||Only links to the actual FMG page and back to the wiki. Should be removed|
|2021-09-15||Confluence||Administration||DSTU2 Ballot to Final breaking changes||Y||Unless there is some important reason for these to remain, they seem out of place.|
|2021-09-15||Confluence||Administration||DSTU2 Technical Correction 1 Tasks||Y||See above|
|2021-09-27||Confluence||Designers||Resource Proposals||Y||the Resource Proposals by Category section seems to list several labels that aren't related to Resource Proposals|
|2021-09-27||Confluence||Designers||Resource Types||Y||Could potentially be restructured so that every listed Resource Type could be a subpage and discussion around the Resource Type could be in the comments. Unlikely to be worth the effort though.|
|2021-09-27||Confluence||Designers||FHIR Spreadsheet Authoring||N|
|2021-09-29||Confluence||Designers||Guide to Designing Resources||Y||Review if all necessary content has been moved over from https://wiki.hl7.org/Authoring_FHIR_Resources. If it has, remove the Todo text.|
|2021-09-29||Confluence||Designers||Managing Overlap Between Resources||Y||This section only has a background, and a note to migrate more content. That is also all the content on the wiki page.|
|2021-09-29||Confluence||Designers||FHIR Build Process||N|
|2021-09-29||Confluence||Designers||HL7 Process for Publishing a FHIR IG||N|
|2021-09-29||Confluence||Designers||FHIR Implementation Guide Process Flow||N|
|2021-09-29||Confluence||Designers||IG Proposals||Y||The IG Proposals by Category section seems to list several labels that aren't related to IG proposals|
|2021-09-29||Confluence||Designers||Profile Proposals||Y||The Profile Proposals by Category section seems to list several labels that aren't related to Profile proposals.|
|2021-09-29||Confluence||Designers||FHIR Profile and IG Balloting||N|
|2021-09-29||Confluence||Designers||FHIR Implementation Guides - Planned Balloting/Publishing||N|
|2021-09-29||Confluence||Designers||FHIR Implementation Guide Publishing Requirements||N|
|2021-09-29||Confluence||Designers||HL7 QA process for FHIR IGs||Y||I believe this is up to date, but I'm not certain.|
|2021-09-29||Confluence||Designers||IG Templates||Y||Does this need to be its own page? Or could it be part of another page?|
|2021-09-29||Confluence||Designers||Implementation Guide Parameters||N|
|2021-09-29||Confluence||Designers||IG Publisher Documentation||N|
|2021-09-29||Confluence||Designers||FHIR Liquid Profile||N|
|2021-09-29||Confluence||Designers||FHIR IG PackageList doco||N|
|2021-09-29||Confluence||Designers||NPM Package Specification||N|
|2021-09-29||Confluence||Designers||FHIR Package Cache||N|
|2021-09-29||Confluence||Designers||FHIR Profile Authoring||Y||Out of date information.|
|2021-09-29||Confluence||Designers||FHIR Spreadsheet Profile Authoring||Y||Is this out of date too?|
|2021-09-29||Confluence||Designers||FHIR Tooling Ecosystem||N|
|2021-09-29||Confluence||Designers||FHIR Tools Registry||Y||Are there any more tools to add to this list?|
|2021-09-29||Confluence||Designers||GIT Conflict Resolution Documentation||N|
|2021-09-29||Confluence||Designers||SMART Web Messaging||N|
|2021-09-29||Confluence||Designers||FHIR Package Registry User Documentation||Y||This page should be completed and corrected if necessary and then the warning that it is incomplete can be removed.|
|2021-09-29||Confluence||Designers||FHIR IG QA Monitoring||N|
|2021-09-29||Confluence||Designers||FHIR Core FMM Support||N|
|2021-09-29||Confluence||Designers||Process for Publishing a FHIR Implementation Guide (for non-HL7 IGs)||N|
|2021-09-29||Confluence||Designers||tx.fhir.org Documentation||N||Grahame created this page on the 24th. So it's definitely up to date.|
|Confluence||Implementers||Blogs||N||Doesn't currently need an update but probably will in the future.|
|Confluence||Implementers||Change Requests||Y||This page seems redundant with the main page on submitting specification feedback (Specification Feedback) Could just be replaced by a link to that page from the main FHIR space.|
|Confluence||Implementers||Chat.fhir.org Community Expectations||N|
|Confluence||Implementers||Clinicians on FHIR||Y||Just links to the PC Clinicians on FHIR page. Should just be a link to that page from the main FHIR space.|
|Confluence||Implementers||Conformance QA Criteria||N|
|Confluence||Implementers||Digital Signatures||Y||Old content (claims to be around coming to a resolution for a gforge tracker|
|Confluence||Implementers||Endpoint directory implementations||N|
|Confluence||Implementers||FHIR Code of Conduct||Y|
|Confluence||Implementers||FHIR Community Process||N|
|Confluence||Implementers||FHIR Intellectual Property Rules||N|
|Confluence||Implementers||FHIR Maturity Model||N|
|Confluence||Implementers||FHIR Rules for Asking Questions||Y||Suggest changing page name to "FHIR Guidelines for Asking Questions"|
|Confluence||Implementers||Getting Involved||Y||Needs text for the two "... to do ..." sections|
|Confluence||Implementers||IGs from other Organizations||Y||Last updated in 2019. Either needs updating or scrapping.|
|Confluence||Implementers||Implementer Support||Y||Last updated in 2019. Some links to wiki content. Seems to have overlap with other pages, especially FHIR Rules for Asking Questions|
|Confluence||Implementers||Interversion Compatibility||Y||According to the comments in 2019 this page is linked to in the FHIR spec. If that is still the case then either the page and the reference should be dropped or the page should be updated with whatever appropriate information is required.|
|Confluence||Implementers||Mailing List Instructions||Y||Unsure if this page is really needed|
|Confluence||Implementers||Migrating OIDs to FHIR||Y||Low priority. I think this content is up to date but I'm unsure.|
|Confluence||Implementers||Open Source Implementations||N|
|Confluence||Implementers||Posting the FHIR specification on hl7.org||Y||Low priority. Content seems up to date, but I'm unsure.|
|Confluence||Implementers||Public FHIR Validation Services||N|
|Confluence||Implementers||Public Test Servers||N|
|Confluence||Implementers||R2-R3 Transformations||Y||Page either needs updating or scrapping|
|Confluence||Implementers||R3-R4 Transformations||Y||Page says that the page has not yet been migrated from the wiki, though also correctly notes that the wiki page has no information on it at all. Either needs content or scrapping|
|Confluence||Implementers||Testing Platforms||Y||Last edited in 2019. I don't know if there are any updates needed but I don't think so?|
|Confluence||Implementers||Using the FHIR Mapping Language||N|
|Confluence||Implementers||Using the FHIR Validator||N|
|Confluence||Implementers||Registering Code Systems||Y||Page needs to be developed. Alternatively dropped in favour of UTG or HTA pages?|
|Confluence||Implementers||SMART on FHIR server implementations||N|
The bulk of the content for this page has yet to be migrated from http://wiki.hl7.org/index.php?title=FHIR