This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Fresh Look"
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
** simplified wire format (end-to-end greening) | ** simplified wire format (end-to-end greening) | ||
*William/Michael | *William/Michael | ||
| − | ** Clear separation of infrastructure and clinical content. (or clear separation of definitional knowledge and effective exchange - ** Registry of templates / models / DCM / archetypes needs to be operational asap | + | ** Clear separation of infrastructure and clinical content. (or clear separation of definitional knowledge and effective exchange - without breaking the connection) |
| + | ** Registry of templates / models / DCM / archetypes needs to be operational asap | ||
*** Can we make them available through a website/wiki? Less computable metadata, but quicker availability. (Gerald) | *** Can we make them available through a website/wiki? Less computable metadata, but quicker availability. (Gerald) | ||
*** OpenEHR has one. What is it that you want this one to achieve? (Grahame) http://www.openehr.org/knowledge/ | *** OpenEHR has one. What is it that you want this one to achieve? (Grahame) http://www.openehr.org/knowledge/ | ||
| Line 26: | Line 27: | ||
*** US National Cancer Institute: https://cdebrowser.nci.nih.gov/CDEBrowser/ | *** US National Cancer Institute: https://cdebrowser.nci.nih.gov/CDEBrowser/ | ||
*** Tolven | *** Tolven | ||
| − | |||
** Proper rules for transformations from different model artifacts to other artifacts, and validation of these. | ** Proper rules for transformations from different model artifacts to other artifacts, and validation of these. | ||
** Clear migration strategy, which is tested to work, before changing HL7 v3 proper to not frustrate the ongoing implementations which are now just starting to be moving ahead (Alexander) | ** Clear migration strategy, which is tested to work, before changing HL7 v3 proper to not frustrate the ongoing implementations which are now just starting to be moving ahead (Alexander) | ||
Revision as of 15:24, 19 May 2011
Note: Please keep the content on this page polite, and insightful. Content here is public, and also community moderated.
Triage
Please add your points as a bullet under here. Links to other pages welcome.
Wishlist items
- Grahame: Keep it simple as can be - implementers first
- Ann's list of 4:
- PIIM
- Implementer's Guides
- What exactly does this mean? Implementer vs Implementation guide .. Rene spronk
- greenCDA
- simplified wire format (end-to-end greening)
- William/Michael
- Clear separation of infrastructure and clinical content. (or clear separation of definitional knowledge and effective exchange - without breaking the connection)
- Registry of templates / models / DCM / archetypes needs to be operational asap
- Can we make them available through a website/wiki? Less computable metadata, but quicker availability. (Gerald)
- OpenEHR has one. What is it that you want this one to achieve? (Grahame) http://www.openehr.org/knowledge/
- Netherlands has two:
- one in DCM format: http://www.eenheidvantaal.nl/
- two in HL7 v3 R-MIM format http://www.zorginformatiemodel.nl and http://www.sre.nl/web/show/id=132128
- CDISC work on Share: http://http://www.cdisc.org/cdisc-share
- Korea EHR project: http://www.clinicalcontentsmodel.org
- Intermountain Healthcare: http://intermountainhealthcare.org/CEM/Pages/LicenseAgreement.aspx
- US National Cancer Institute: https://cdebrowser.nci.nih.gov/CDEBrowser/
- Tolven
- Proper rules for transformations from different model artifacts to other artifacts, and validation of these.
- Clear migration strategy, which is tested to work, before changing HL7 v3 proper to not frustrate the ongoing implementations which are now just starting to be moving ahead (Alexander)
- Rene: implementers either need PIIM for MDA implementations, OR simplified wire format - with normative associated schema.
- This is AND/OR, not XOR, correct? (Gerald)
- Yes, AND/OR, although most implementers will choose to use one XOR the other (e.g. if the scope of the project is limited to a very few models, use a simplified wire format. If the project uses tons of models, use MDA). HL7 needs to provide implementers with both options. (Rene)
Concrete next Steps
For actual things that should be done
- ahh.... ?
