July 25, 2017, Tuesday, 205

Principles, Policies and Guidelines

From Wikicare

Jump to: navigation, search

Do not edit this page! If you want to propose amendments, changes, additions, deletions, etc. please go to Proposing policy amendments and follow the instructions.

Care2x is a collaborative open project. Both its founder and participating members have a common mission:

We strive to develop the most useful and most practical  integrated 
healthcare information system which is open for others to develop further.


Key principles

  • The patient is the center of all our activities
  • Care2x does not and will not discriminate any nation, continent, language, race, religion, culture nor socio-political-economic systems.
  • Care2x is not a political platform. It must not be abused as a launchpad for any political directions.
  • Care2x is not a political instrument. It must not be abused as an instrument for any political purposes.
  • Care2x is not a religion. It will stay neutral to religious beliefs.
  • Care2x is not a weapon and must not be abused as such.
  • Care2x will respect other "standards" even if it may or may not propose its own standard soon or in the future.
  • Care2x will try to integrate other "standards" where appropriate.
  • Care2x will not enter into a competitive race against similar projects but instead try to create a channel to communicate with other applications.

See also Dealing with policy violations

Key Policies

To participate and contribute to Care2x, you don't need to read every policy before you contribute! However, the following policies are key to a productive Care2x participation, and the sooner you get to grips with them, the better.

  1. Mind the licenses. Care2x is licensed with GNU GPL. Submitting code with incompatible licenses threatens our objective to build a truly free integrated healthcare information system that anyone can redistribute, and could lead to legal problems.
  2. Care2x is an integrated healthcare information system. The other description "Integrated Healthcare Environment" is synonymous. Its goals go no further.
  3. Avoid bias. Information should be written from a neutral point of view, representing differing views on a subject fairly and sympathetically.
  4. Respect other participants. Care2x participants come from many different countries and cultures, and have widely different views. Treating others with respect is key to collaborating effectively in building an integrated healthcare system.
  5. Avoid rebranding. (Do not kill the hen that lays the golden eggs) Rebranding or renaming Care2x threatens to sow confusion among current and potential users and is counterproductive for both Care2x and the rebranded version. Also, rebranding or renaming is not a letigimate fork as defined in the GNU GPL license and must be avoided.

policies on commercial entities

..... coming soon .....


Policy formulation

Care2x's policy is formulated mostly by consensus. This consensus may be reached through two channels: open debate over difficult questions, or as a result of established practice. In many cases, policies are not always formally written down right away. Hence, the statements on this and other pages about Care2x's policy are intended to describe existing community norms that have developed over time.

Policy issues may be formulated and debated on mailing lists and the forum. If a policy may be controversial, it should always be discussed before being adopted.

Policies that result from established practice are sometimes harder to identify. If there is no objection to the practice, it may be difficult to sustain community attention long enough for a formal process of adopting it as policy. In this situation, the best solution may be to document existing practice on an appropriate page. This then provides a location to discuss the practice and possible changes to the policy, and it also allows people to cite a source for the policy if necessary.


A formulated policy can still be vetoed by the project leader. He may or may not use this veto power and hopes that he may not need to use it at all. However, once a policy is vetoed, only the project leader can revert the veto.

breaking up a deadlock

In case of a deadlock where an unbreakable cycle of formulation-veto-reformulation-veto develops, the project leader can exercise dictatorial power and decides the final policy.

Policy enforcement

You are the Care2x policy enforcement officer. Although Care2x has a central, top-down mechanism whereby the day-to-day progress on the project is monitored and approved, this mechanism in the form of project leader cannot do all the work necessary to enforce policies. Instead, active participants make the development and correct problem as they see it. So the participants are both developer and troubleshooter.

Most policies and guidelines are thus enforced by individual developers, and discussing matters with each other. Some policies are also enforced by blocks and/or rejection (notably as a mechanism for dealing with spam and vandalism) by admins. In extreme cases the project leader may organize an adhoc commitee to deal with highly disruptive situations, as part of the general dispute resolution procedure. As a last recourse, the project leader can exercise dictatorial powers.

Specific guidelines


  • Contribute what you can
  • Just do it
  • Be bold in modifying the code
  • Build the documentation Wiki
  • Ignore all the rules


  • Integrate changes
  • Define and describe
  • [State the obvious
  • Cite sources: point the reader to authoritative references (and list them properly)
  • Check your data
  • Follow coding convention
  • Debug your code
  • Patch your bugs
  • Document your code

Mind your behavior

  • Avoid profanity
  • No politics
  • No personal attacks
  • No namedropping
  • No unverifiable info
  • Stay on topic
  • No legal threats
  • Log in before editing the documentation Wiki
  • No offensive usernames
  • Do not discourage the newcomers
  • Create articles about yourself
  • Blocking policy
  • Rejection policy
  • Dealing with administration issues


  • Manual of style
  • Use color sparingly
  • Balance parts of a module's page

Dealing with policy violations

Although Care2x is open, collaborative and practices non-discrimination, it also recognizes the fact that it needs to protect itself from factors that might threaten to destruct or destabilize the integrity of the project. We agree that open collaboration is not a permission to anarchy.

policy violations

Policy violations differ in form and extent and must be dealt with in cases to case basis.

self protection

When proven that Care2x is being compromised as a result of policy violations, it will engage following protective mechanisms:

  • Blocking participation of violators.
  • Removal of violators from the project (mailing lists, forums, websites, etc).
  • Refusal to sanction violators or violating media.
  • Withdrawal of previously given sanctions.
  • In extreme cases, Care2x will:
    • Publicly broadcast the case and its details.
    • Take legal actions in court.

how violation cases are processed

  1. The violation and/or violator is reported to the admin.
  2. The violating act or media is verified.
  3. The violator is contacted and asked for his side of the case.
  4. If violation is proven, the violator will be asked several times (at least 3 times) to make corrections.
  5. If the violator refuses to make the corrections, the process of deciding which protective measure must be taken will begin.

how protective measures are decided

The appropriate measure will be the result of a concensus of a least three persons. In case of deadlock on the face of an aggravated case, the project leader will make the decision without the need of concensus.