dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #20315
[Branch ~dhis2-devs-core/dhis2/trunk] Rev 9216: FRED-API: minor change
------------------------------------------------------------
revno: 9216
committer: Morten Olav Hansen <mortenoh@xxxxxxxxx>
branch nick: dhis2
timestamp: Fri 2012-12-07 23:48:22 +0300
message:
FRED-API: minor change
modified:
dhis-2/dhis-web/dhis-web-api-fred/src/main/webapp/WEB-INF/api-fred-velocity/v1/index.vm
--
lp:dhis2
https://code.launchpad.net/~dhis2-devs-core/dhis2/trunk
Your team DHIS 2 developers is subscribed to branch lp:dhis2.
To unsubscribe from this branch go to https://code.launchpad.net/~dhis2-devs-core/dhis2/trunk/+edit-subscription
=== modified file 'dhis-2/dhis-web/dhis-web-api-fred/src/main/webapp/WEB-INF/api-fred-velocity/v1/index.vm'
--- dhis-2/dhis-web/dhis-web-api-fred/src/main/webapp/WEB-INF/api-fred-velocity/v1/index.vm 2012-12-07 20:42:02 +0000
+++ dhis-2/dhis-web/dhis-web-api-fred/src/main/webapp/WEB-INF/api-fred-velocity/v1/index.vm 2012-12-07 20:48:22 +0000
@@ -2,21 +2,22 @@
<div class="hero-unit">
<h2>Facility Registry Expansion Development</h2>
- <p style="font-size: 0.8em;">The Open Facility Registry Service Project or FRED - "Facility Registry Expansion Development" will model the benefits of an NHIS
- Health Information Exchange (HIE) and provide a roadmap for implementation of the full range of NHIS components. The development
- and documentation of a Facility Registry Service (a master facilities list along with documented methods of interoperability)
- will provide a common and replicable solution for integrated e/mHealth systems. In collaboration with national entities,
- academia, solution providers, NGOs (NetHope members) and donors, we will develop a standards-based service that reflect national
- policies and regulation, using the subset of the Facility Registry Service to illustrate how the rest of the NHIS components can
- be similarly orchestrated. In a repeatable fashion, FRED will complete the design, development, and reference implementation of
- a Facility Registry Service and prepare for its interoperability with existing key e/mHealth tools in multiple countries during
- the next 9-12 months. FRED will provide an open source, standards-based, repeatable approach to the implementation of a Facility
- Registry Service; it will at the same time accommodate unique national requirements as well as allow for continuous and
- evolutionary improvements.
+ <p style="font-size: 0.8em;">The Open Facility Registry Service Project or FRED - "Facility Registry Expansion Development" will
+ model the benefits of an NHIS Health Information Exchange (HIE) and provide a roadmap for implementation of the full range of
+ NHIS components. The development and documentation of a Facility Registry Service (a master facilities list along with
+ documented methods of interoperability) will provide a common and replicable solution for integrated e/mHealth systems. In
+ collaboration with national entities,academia, solution providers, NGOs (NetHope members) and donors, we will develop a
+ standards-based service that reflect national policies and regulation, using the subset of the Facility Registry Service to
+ illustrate how the rest of the NHIS components can be similarly orchestrated. In a repeatable fashion, FRED will complete the
+ design, development, and reference implementation of a Facility Registry Service and prepare for its interoperability with
+ existing key e/mHealth tools in multiple countries during the next 9-12 months. FRED will provide an open source,
+ standards-based, repeatable approach to the implementation of a Facility Registry Service; it will at the same time accommodate
+ unique national requirements as well as allow for continuous and evolutionary improvements.
</p>
<p>
- <a class="btn btn-primary btn-large" href="http://facility-registry-api.readthedocs.org/en/latest/api_specifications.html">
+ <a style="font-size: 0.8em;" class="btn btn-primary btn-large"
+ href="http://facility-registry-api.readthedocs.org/en/latest/api_specifications.html">
Read the specification »
</a>
</p>