This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Proposed new Topic: Application Registry"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 11: | Line 11: | ||
[[Image:Device register zorgtoepassing ENTRY.gif|400px|center|thumbnail|Entry point for Application registry (new topic)]] | [[Image:Device register zorgtoepassing ENTRY.gif|400px|center|thumbnail|Entry point for Application registry (new topic)]] | ||
| + | |||
| + | ==Discussion== | ||
| + | *20090112 Q2, Orlando: PA feels that, even when there are areas of overlap (this static model is covered by the PM D-MIM, it fits in the general registry pattern, the PM D-MIM suggests it was the intent of PM to create such registries) that this is out of scope of the PM material. This is not about medical devices, so this is out of scope of the Devices WG. Maye Shared Messages might be appropriate. For technical reasons this proposal is rejected: there is no second implementer that would commit to implementing the proposed solution. | ||
Revision as of 18:41, 13 January 2009
(Organization and provider part of this proposal have been taken care of. Content has been removed from the proposal.)
Application Topic
High-level walkthrough: the top half of this model is new, the bottom half is based on the current PRPM D-MIM. The tophalf of the model has been added to associated the parties (AssignedEntity) with the application(s) (QualifiedApplicationRole) that they use to exchange interactions (identified by InformEvent). The Inform class plays the linking pin in the model: it expresses that the AssignedEntity expects to inform, and expects to be informed, using a certain software application, by means of a set of interactions.
R-MIMs
Discussion
- 20090112 Q2, Orlando: PA feels that, even when there are areas of overlap (this static model is covered by the PM D-MIM, it fits in the general registry pattern, the PM D-MIM suggests it was the intent of PM to create such registries) that this is out of scope of the PM material. This is not about medical devices, so this is out of scope of the Devices WG. Maye Shared Messages might be appropriate. For technical reasons this proposal is rejected: there is no second implementer that would commit to implementing the proposed solution.
