Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Contents

Access to uploading/downloading of selected registers is restricted to the users with the the system role of IMIS Administrator ( the register of locations) or with a role including an access to Tools/Registers.

Navigation

All functionality for use with the administration of uploading/downloading of selected registers can be found under the main menu Tools, sub menu Registers.

Clicking on the sub menu Registers re-directs the current user to the Registers Page: (Img. 197)

Registers page

The Registers Page is divided into eight sections: (Img. 198)

  1. Upload of the list of diagnoses

  • Browse

    Select from a file in the XML format serving as a source for uploading of the list of diagnoses. Mandatory.

  • Strategy

    Select a desired strategy for uploading of the list of diagnoses. The following options are available:

  • Insert Only

    Uploads only diagnoses that are not yet included in the list of diagnoses

  • Update Only

Updates only diagnoses that are already included in the list of diagnoses

  • Insert and Update

Uploads diagnoses that are not yet included in the list of diagnoses and updates diagnoses that are already included in the list of diagnoses

  • Insert, Update and Delete

Uploads diagnoses that are not yet included in the list of diagnoses, updates diagnoses that are already included in the list of diagnoses and deletes diagnose that are not included in the source file

  • Dry Run

    If checked, only diagnostics is provided without real uploading.

  • Upload

    By clicking on the Upload button, a prompt popup message will appear, require a user to agree or disagree:(Upload Diagnoses)

    If user agrees the selected file containing diagnoses will be uploaded.

    A statistics on the number of inserted/updated diagnoses appears:

    (Statistics on uploaded diagnoses).

If there are errors an error protocol appears: (Error protocol on uploaded diagnoses)

DTD definition of the XML file for uploading/downloading of diagnoses:

<!DOCTYPE Diagnoses> [

<!ELEMENT Diagnoses (Diagnosis)*>

<!ELEMENT Diagnosis (DiagnosisCode, DiagnosisName)>

< !ELEMENT DiagnosisCode (#CDATA)>

< !ELEMENT DiagnosisName (#CDATA)>

]>

  1. Upload of the register of locations

  • Browse

    Select from a file in the XML format serving as a source for uploading of the register of locations. Mandatory.

  • Strategy

    Select a desired strategy for uploading of the register of locations. The following options are available:

  • Insert Only

    Uploads only locations that are not yet included in the register of locations

  • Update Only

    Updates only locations that are already included in the register of locations

  • Insert and Update

    Uploads locations that are not yet included in the register of locations and updates locations that are already included in the register of locations

  • Dry Run

    If checked only diagnostics is provided without real uploading.

  • Upload

    By clicking on the Upload button, a prompt popup message will appear, require a user to agree or disagree (Upload Locations). If user agrees the selected file containing locations will be uploaded.

    A statistics on the number of inserted/updated locations appears (Upload Locations statistics)

    If there are errors an error protocol appears (Upload Locations error)

    DTD definition of the XML file for uploading/downloading of locations:

    <!DOCTYPE Locations> [

    <!ELEMENT Locations (Regions, Districts, Municipalities, Villages)>

    <!ELEMENT Regions (Region*)>

    <!ELEMENT Region (RegionCode, RegionName)>

    < !ELEMENT RegionCode (#CDATA)>

    < !ELEMENT RegionName (#CDATA)>

    <!ELEMENT Districts (District*)>

    <!ELEMENT District (RegionCode,DistrictCode, DistrictName)>

    < !ELEMENT RegionCode (#CDATA)>

    < !ELEMENT DistrictCode (#CDATA)>

    < !ELEMENT DistrictName (#CDATA)>

    <!ELEMENT Municipalities (Municipality*)>

    <!ELEMENT Municipality (DistrictCode,MunicipalityCode, MunicipalityName)>

    < !ELEMENT DistrictCode (#CDATA)>

    < !ELEMENT MunicipalityCode (#CDATA)>

    < !ELEMENT MunicipalityName (#CDATA)>

    <!ELEMENT Villages (Village*)>

    <!ELEMENT Village (MunicipalityCode,VillageCode, VillageName,MalePopulation ?, FemalePopulation ?, OtherPopulation,Families ?)>

    < !ELEMENT MunicipalityCode (#CDATA)>

    < !ELEMENT VillageCode (#CDATA)>

    < !ELEMENT VillageName (#CDATA)>

    < !ELEMENT MalePopulation (#CDATA)>

    < !ELEMENT FemalePopulation (#CDATA)>

    < !ELEMENT OtherPopulation (#CDATA)>

    < !ELEMENT Families (#CDATA)>

    ]>

  1. Upload of the register of health facilities

  • Browse

    Select from a file in the XML format serving as a source for uploading of the register of health facilities. Mandatory.

  • Strategy

    Select a desired strategy for uploading of the register of health facilities. The following options are available:

  • Insert Only

    Uploads only health facilities that are not yet included in the register of health facilities

  • Update Only

    Updates only health facilities that are already included in the register of health facilities

  • Insert and Update

    Uploads health facilities that are not yet included in the register of health facilities and updates health facilities that are already included in the register of health facilities

  • Dry Run

    If checked only diagnostics is provided without real uploading.

  • Upload

    By clicking on the Upload button, a prompt popup message will appear, require a user to agree or disagree: (Upload Health Facilities) If user agrees the selected file containing locations will be uploaded.

    A statistics on the number of inserted/updated health facilities appears.

    If there are errors an error protocol appears.

    DTD definition of the XML file for uploading/downloading of health facilities:

    <!DOCTYPE HealthFacilities> [

    <!ELEMENT HealthFacilities (HealthFacilityDetails,CatchmentsDetails)>

    <!ELEMENT HealthFacilityDetails (HealthFacility)*>

    <!ELEMENT HealthFacility (LegalForm, Level, Sublevel, Code, Name, Address, DistrictCode, DistrictName, Phone, Fax, Email, CareType, AccountCode, ItemPriceListName. ServicePricelistName)>

    <!ELEMENT LegalForm (D| C|G|P)>

    <!ELEMENT Level (D|C|H)>

    <!ELEMENT SubLevel (I|N|R)>

    <!ELEMENT Code (#CDATA)>

    <!ELEMENT Name (#CDATA)>

    <!ELEMENT Address (#CDATA)>

    <!ELEMENT DistrictCode (#CDATA)>

    <!ELEMENT DistrictName (#CDATA)>

    <!ELEMENT Phone (#CDATA)>

    <!ELEMENT Fax (#CDATA)>

    <!ELEMENT Email (#CDATA)>

    <!ELEMENT CareType (I|N|B)>

    <!ELEMENT AccountCode (#CDATA)>

    <!ELEMENT ItemPriceListName (#CDATA)>

    <!ELEMENT ServicePriceListName (#CDATA)>

    <!ELEMENT CatchmentsDetails(Catchment*)>

    <!ELEMENT Catchment (HFCode,VillageCode, VillageName, Percentage)>

    <!ELEMENT HFCode (#CDATA)>

    <!ELEMENT VillageCode (#CDATA)>

    <!ELEMENT VillageName (#CDATA)>

    <!ELEMENT Percentage (#CDATA)>

    ]>

  1. Download of the list diagnoses

  • Download

    By clicking on the Download button, a prompt popup message will appear, require a user to specify whether the XML file with downloaded list of diagnoses should be opened or saved or canceled: (Download Diagnoses)

  1. Download of the register of locations

  • Download

    By clicking on the Download button, a prompt popup message will appear, require a user to specify whether the XML file with downloaded register of locations should be opened or saved or canceled (Download locations)

  1. Download of the register of health facilities

  • Download

    By clicking on the Download button, a prompt popup message will appear, require a user to specify whether the XML file with downloaded canceled (Download facilities)

  1. Buttons

  • Cancel

    By clicking on Cancel button, user will be re-directed to the Home page.

  1. Information Panel

The Information Panel is used to display messages back to the user.




  • No labels