This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Workflow Minutes CC 20170405"
Jump to navigation
Jump to search
(Created page with "{{subst::FHIR Workflow Template for Minutes}}") |
|||
| Line 8: | Line 8: | ||
==Attendees== | ==Attendees== | ||
| − | * | + | *Lloyd Mckenzie (chair/scribe) |
| − | * | + | *John Hatem |
| + | *Yunwei Wang | ||
| + | *Jeffrey Danford | ||
| + | *Jose Costa Teixeira | ||
| − | == | + | ==Call audio== |
| − | + | Will try to use GotoMeeting Audio for future calls | |
| − | |||
| − | |||
| − | |||
| + | ==Order Catalog== | ||
| + | Update from Jose | ||
| + | * Ability to identify what products/services "can be ordered" in a given institution | ||
| + | * Catalogue of medication, devices, specimen types, protocols | ||
| + | * Rather than a "Catalog" resource - need a resource to present a "collection of things"; Need a definitional resource to represent each item in the list with metadata such as Status, pointers to what's being replaced or alternatives, does it group other entities | ||
| + | *Talked about use of List rather than Composition - some of the Definition pattern elements may make sense on List | ||
| + | *There's a difference between what we capture in the formulary (catalog) vs. what's in the knowledgebase | ||
| + | *Multiple sets of information - scientific (substances and all of the knowledge around them), commercial (who makes, distributes, etc), 'official' (what are we allowed to use) | ||
| + | * There are use-cases to capture "kinds" and "instances" at a reference level - just enough information to know what you're talking about. There's also a use-case to capture the "definition" which is far more information and focuses on "knowledge" | ||
==Adjournment== | ==Adjournment== | ||
Latest revision as of 18:59, 5 April 2017
FHIR Workflow Conference Call 3:00PM Eastern Time (Date above)
Return to FHIR Workflow Minutes
Agenda
- Approve Minutes Prior Meeting on mm/dd
Attendees
- Lloyd Mckenzie (chair/scribe)
- John Hatem
- Yunwei Wang
- Jeffrey Danford
- Jose Costa Teixeira
Call audio
Will try to use GotoMeeting Audio for future calls
Order Catalog
Update from Jose
- Ability to identify what products/services "can be ordered" in a given institution
- Catalogue of medication, devices, specimen types, protocols
- Rather than a "Catalog" resource - need a resource to present a "collection of things"; Need a definitional resource to represent each item in the list with metadata such as Status, pointers to what's being replaced or alternatives, does it group other entities
- Talked about use of List rather than Composition - some of the Definition pattern elements may make sense on List
- There's a difference between what we capture in the formulary (catalog) vs. what's in the knowledgebase
- Multiple sets of information - scientific (substances and all of the knowledge around them), commercial (who makes, distributes, etc), 'official' (what are we allowed to use)
- There are use-cases to capture "kinds" and "instances" at a reference level - just enough information to know what you're talking about. There's also a use-case to capture the "definition" which is far more information and focuses on "knowledge"
