1. A method of managing a treatment plan on a computer network, comprising:
making a database of efficacy data accessible to a provider interface;
receiving a work-up from the provider interface;
creating a treatment plan on the database from the work-up received from the provider interface;
assigning an approval status to the treatment plan;
sending an approval notice relating to the treatment plan to said provider interface and to a pharmacy interface, wherein the approval notice relates to the treatment plan;
invoking a surveillance plan to track and capture outcome information generated from the implementation of the treatment plan;
storing a plurality outcome information received from at least one of: (a) a payer interface; (b) the pharmacy interface; (c) the provider interface; and (d) a patient interface; and
automatically updating the efficacy data using the outcome information.
2. The method of claim 1, further comprising:
automatically changing the status of the treatment plan in response to the stored outcome information.
3. The method of claim 1, wherein the creation of the treatment plan is automatically influenced by an efficacy datum and a patient datum.
4. The method of claim 3, wherein the creation of the treatment plan is automatically influenced by a plurality of patient data, including business information, medical information, and surveillance information.
5. The method of claim 1, wherein the creation of the treatment plan is automatically influenced by a payer rule, a provider rule, a patient rule, and a pharmacy rule.
6. The method of claim 1, wherein the treatment plan relates to a condition of cancer, wherein the treatment plan includes a chemotherapy as a treatment component, and wherein the treatment plan is automatically modified before the completion of the treatment plan.
7. The method of claim 1, wherein the surveillance plan relates to a cancer condition, wherein the surveillance plan includes a pharmaceutical product, and wherein the surveillance plan is automatically modified before the completion of the surveillance plan.
8. The method of claim 1, wherein the work-up is selected from a pre-approved regimen selection.
9. The method of claim 1, further comprising an automatic sending of a notice to at least one of: (a) the payer interface; (b) the provider interface; (c) the patient interface; and (d) the pharmacy interface in response to a failure to comply with at least one of: (i) the treatment plan; and (ii) the surveillance plan.
10. The method of claim 1, wherein a surveillance plan is automatically created without human intervention after the approval of the treatment plan.
11. A healthcare management system, comprising:
an application and database residing on a server;
said database including a plurality of regimen data, a plurality efficacy data, a plurality of interaction data, a plurality of patient data, a treatment plan, and a surveillance plan;
said application providing for a patient interface, a provider interface, a payer interface, and a pharmacist interface;
wherein said treatment plan is selected from said provider interface and is selectively and automatically influenced by said patient data, and said efficacy data.
12. The system of claim 11, wherein said treatment plan selected from said provider interface is a pre-approved treatment plan.
13. The system of claim 11, wherein said surveillance plan is approved separate from the approval of said treatment plan.
14. The system of claim 11, wherein said efficacy data and said regimen data are updated before the completion of said surveillance plan.
15. The system of claim 11, wherein a status associated with said treatment plan is modified before the completion of said treatment plan.
16. The system of claim 11, said database further including a payer rule received thru said payer interface, wherein said payer rule influences said application to reject a work-up.
17. The system of claim 11, said application further providing for the capture of a plurality of outcome data, wherein receipt of said outcome data triggers a modification to said surveillance plan.
18. The system of claim 11, wherein the treatment plan relates to a condition of cancer, wherein the treatment plan includes a chemotherapy as a treatment component, and wherein the treatment plan is pre-approved from a regimen selection made with said provider interface.
19. The system of claim 11, wherein said efficacy data is automatically updated by said application.
20. A health care management system, comprising:
a provider subsystem, said provider subsystem providing for the scheduling of an examination with a patient, the creation of a work-up using a regimen selected using a provider interface, and the submission of the work-up for approval as a treatment plan, wherein the schedule of the examination, the work-up are stored on a database accessible by a payer subsystem;
said payer subsystem providing for populating a database with a plurality of regimen data and a plurality of efficacy data, wherein said payer subsystem further provided for approving a work-up as a treatment plan and transmitting an order corresponding to the treatment plan to a pharmacy subsystem;
said pharmacy subsystem providing for initiating at least one shipment and at least one notification;
wherein said treatment plan is associated with a surveillance plan, and wherein said system automatically collects a plurality of outcome data in accordance with said surveillance plan.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A linear motor armature comprising:
an armature core including:
a yoke extending straight; and
a plurality of pole teeth fixed to the yoke and disposed along the yoke and spaced in a longitudinal direction of the yoke such that a slot is formed between two adjacent pole teeth;
a plurality of excitation windings at least partially disposed in the slots formed in the armature core to excite the plurality of pole teeth; and
a cooling device configured to cool the plurality of excitation windings using a coolant, the cooling device comprising:
a first cooling conduit including:
a first main conduit running zigzag, the first main conduit including a plurality of straight conduits extending inside the slots and a plurality of coupling conduits, each of which couples two adjacent straight conduits such that the plurality of straight conduits are connected in series; and
a first pair of connecting conduits provided at both ends of the first main conduit;
a second cooling conduit including:
a second main conduit running zigzag and opposed to the first main conduit via the plurality of excitation windings, the second main conduit including a plurality of straight conduits extending inside the slots and a plurality of coupling conduits, each of which couples two adjacent straight conduits such that the plurality of straight conduits are connected in series; and
a second pair of connecting conduits provided at both ends of the second main conduit; and
a manifold provided to supply the coolant to the first cooling conduit and the second cooling conduit, wherein
the manifold and the first and second pairs of connecting conduits are configured such that the coolant is supplied from one connecting conduit of the first pair of connecting conduits and one connecting conduit of the second pair of connecting conduits and discharged from the other connecting conduit of the first pair of connecting conduits and the other connecting conduit of the second pair of connecting conduits.
2. The linear motor armature according to claim 1, wherein:
the manifold is fixed to the armature core and includes one coolant inlet port, two coolant delivery ports each communicating with the one coolant inlet port, one coolant outlet port, and two coolant discharge ports each communicating with the one coolant outlet port; and
the first and second pairs of connecting conduits are shaped such that the one connecting conduit of the first pair of connecting conduits of the first cooling conduit and the one connecting conduit of the second pair of connecting conduits of the second cooling conduit are connected to the two coolant delivery ports, and that the other connecting conduit of the first pair of connecting conduits of the first cooling conduit and the other connecting conduit of the second pair of connecting conduits of the second cooling conduit are connected to the two coolant discharge ports.
3. The linear motor armature according to claim 2, wherein:
the manifold is fixed in the vicinity of one side surface of the armature core that is located in a direction in which the slots extend;
the first and second pairs of connecting conduits are disposed in a connecting conduit installation space located above the one side surface; and
the two coolant delivery ports and the two coolant discharge ports of the manifold each open toward the connecting conduit installation space.
4. The linear motor armature according to claim 3, wherein:
the connecting conduit of the first pair of connecting conduits that extends toward the manifold from a side opposite to a side where the manifold is located and the connecting conduit of the second pair of connecting conduits that extends toward the manifold from a side opposite to the side where the manifold is located intersect each other in the connecting conduit installation space to form an intersecting portion; and
the intersecting portion is at least partially located between the plurality of coupling conduits included in the first main conduit and the plurality of coupling conduits included in the second main conduit.
5. The linear motor armature according to claim 4, wherein:
the plurality of pole teeth include a plurality of wound pole teeth on which the excitation windings are wound and a plurality of non-wound pole teeth on which the excitation windings are not wound; and
the intersecting portion is located above the non-wound pole teeth.
6. The linear motor armature according to claim 4, wherein
the first and second pairs of connecting conduits are disposed such that the coolant flows through one of the first and second main conduits in a direction from the side where the manifold is located to the opposite side, and that the coolant flows through the other of the first and second main conduits in a direction from the opposite side to the side where the manifold is located.
7. The linear motor armature according to claim 1, wherein:
the first and second cooling conduits each have a rectangular cross-sectional shape; and
one of outer surfaces of each of the first and second cooling conduits faces the excitation windings.
8. The linear motor armature according to claim 2, wherein:
the first and second cooling conduits each have a rectangular cross-sectional shape; and
one of outer surfaces of each of the first and second cooling conduits faces the excitation windings.
9. The linear motor armature according to claim 3, wherein:
the first and second cooling conduits each have a rectangular cross-sectional shape; and
one of outer surfaces of each of the first and second cooling conduits faces the excitation windings.
10. The linear motor armature according to claim 4, wherein:
the first and second cooling conduits each have a rectangular cross-sectional shape; and
one of outer surfaces of each of the first and second cooling conduits faces the excitation windings.
11. The linear motor armature according to claim 5, wherein:
the first and second cooling conduits each have a rectangular cross-sectional shape; and
one of outer surfaces of each of the first and second cooling conduits faces the excitation windings.
12. The linear motor armature according to claim 6, wherein:
the first and second cooling conduits each have a rectangular cross-sectional shape; and
one of outer surfaces of each of the first and second cooling conduits faces the excitation windings.