Difference between revisions of "Facilities And Hierarchies proposal"
Jump to navigation
Jump to search
Ucappellini (talk | contribs) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | '''WEBEX MEETING | + | '''WEBEX MEETING 19.11.2018''' |
| − | + | * Luke to prepare a formal list of use cases for the proposal and eventually a data model representing such use cases (to be matched to a FHIR model) | |
| − | * Luke to | + | '''WEBEX MEETING 03.12.2018''' |
| − | + | * Use cases and recommendations are in a [https://docs.google.com/presentation/d/1aZ7vdeDcYmc6SIURggRFcNcwnECqPtXL5ODPnaRzCOA/edit?usp=sharing google doc for comments]. | |
| − | * | + | * Current road map |
| + | ** Define Facilities as an association between Organization and Location and profile that. | ||
| + | ** Add an extension to Organization to allow multiple hierarchies. | ||
| + | *** Since Organization is more conceptual and more inclined to multiple hierarchies is there a need for something similar in Location? | ||
Latest revision as of 17:13, 3 December 2018
WEBEX MEETING 19.11.2018
- Luke to prepare a formal list of use cases for the proposal and eventually a data model representing such use cases (to be matched to a FHIR model)
WEBEX MEETING 03.12.2018
- Use cases and recommendations are in a google doc for comments.
- Current road map
- Define Facilities as an association between Organization and Location and profile that.
- Add an extension to Organization to allow multiple hierarchies.
- Since Organization is more conceptual and more inclined to multiple hierarchies is there a need for something similar in Location?