This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Creation of a Set of AID Whitepapers"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 6: | Line 6: | ||
==Planning== | ==Planning== | ||
| − | *[[Software Implementation of CDA]] | + | *[[Software Implementation of CDA]] |
| − | **Sept | + | **Sept 2014: updating, re-approval in January 2015 |
| − | *[[Persisting FHIR Resources]], January | + | *[[Persisting FHIR Resources]], |
| + | **Sept 2014: Andy will create skeleton verson before meeting in January 2015 | ||
| + | *[[Implementation Guidance for the IVL TS data type]] | ||
| + | **Sept 2014: will need additional review, won't need maintenance once finished | ||
Candidate topics: | Candidate topics: | ||
*v2-v3 migration / mapping, inclusive of recommendations as to how one should 'enrich' current v2 interface to ensure ease of transformability. | *v2-v3 migration / mapping, inclusive of recommendations as to how one should 'enrich' current v2 interface to ensure ease of transformability. | ||
Revision as of 06:23, 18 September 2014
The Creation of a Set of RIMBAA Whitepapers project was established to manage the process of creating a set of whitepapers.
- Note: This is project #550 in the Project Insight tool. Project approved by FTSD on its call of 2010-10-19. Project approved by TSC on its call on 2010-11-08.
Scope
This is a long running (maintenance type) project to create a set of whitepapers with the consensus based findings of the RIMBAA WG as to what the v3 implementation best practices (or: v3 implementation patterns) are.
Planning
- Software Implementation of CDA
- Sept 2014: updating, re-approval in January 2015
- Persisting FHIR Resources,
- Sept 2014: Andy will create skeleton verson before meeting in January 2015
- Implementation Guidance for the IVL TS data type
- Sept 2014: will need additional review, won't need maintenance once finished
Candidate topics:
- v2-v3 migration / mapping, inclusive of recommendations as to how one should 'enrich' current v2 interface to ensure ease of transformability.
