<commit_before>Open eHealth Integration Platform (IPF)
---------------------------------------

The Open eHealth Integration Platform (IPF) is an extension of the Apache Camel 
routing and mediation engine. It has an application programming layer based on 
the Groovy programming language and comes  ... [More]  with comprehensive 
support for message processing and connecting systems in the healthcare domain. 
IPF provides a domain-specific language for building integration solutions from 
Enterprise Integration Patterns.


Getting Started
---------------

- Introduction

http://repo.openehealth.org/confluence/display/ipf/IPF+Introduction

- Building

http://repo.openehealth.org/confluence/display/ipf/IPF+Development

- Tutorials

http://repo.openehealth.org/confluence/display/ipf/IPF+Tutorials


Reference Manual 
----------------

- html (single-page view):

http://repo.openehealth.org/confluence/display/ipf/IPF+reference+-+single

- html (multi-page view):

http://repo.openehealth.org/confluence/display/ipf/IPF+reference+-+multi


Mailing Lists
-------------

- IPF developer mailing list

http://gforge.openehealth.org/mailman/listinfo/ipf-developer (mailman)
http://n2.nabble.com/IPF-developer-f2983467.html             (nabble)

- IPF user mailing list

http://gforge.openehealth.org/mailman/listinfo/ipf-user      (mailman)
http://n2.nabble.com/IPF-user-f2983354.html                  (nabble)


Please help us make the Open eHealth Integration Platform better - 
we appreciate any feedback you may have.

Enjoy!

The IPF team
<commit_msg>documentation links updated<commit_after>Open eHealth Integration Platform (IPF)
---------------------------------------

The Open eHealth Integration Platform (IPF) is an extension of the Apache Camel 
routing and mediation engine. It has an application programming layer based on 
the Groovy programming language and comes  ... [More]  with comprehensive 
support for message processing and connecting systems in the healthcare domain. 
IPF provides a domain-specific language for building integration solutions from 
Enterprise Integration Patterns.


Getting Started
---------------

- Introduction

http://repo.openehealth.org/confluence/display/ipf2/IPF+Introduction

- Building

http://repo.openehealth.org/confluence/display/ipf2/IPF+Development

- Tutorials

http://repo.openehealth.org/confluence/display/ipf2/IPF+Tutorials


Reference Manual 
----------------

- html (single-page view):

http://repo.openehealth.org/confluence/display/ipf2/IPF+reference+-+single

- html (multi-page view):

http://repo.openehealth.org/confluence/display/ipf2/IPF+reference+-+multi


Mailing Lists
-------------

- IPF developer mailing list

http://gforge.openehealth.org/mailman/listinfo/ipf-developer (mailman)
http://n2.nabble.com/IPF-developer-f2983467.html             (nabble)

- IPF user mailing list

http://gforge.openehealth.org/mailman/listinfo/ipf-user      (mailman)
http://n2.nabble.com/IPF-user-f2983354.html                  (nabble)


Please help us make the Open eHealth Integration Platform better - 
we appreciate any feedback you may have.

Enjoy!

The IPF team

{'fraction_non_alphanumeric': 0.13325145839729813, 'fraction_numerical': 0.011360147374884864, 'mean_word_length': 2.731958762886598, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5662738', 'n_tokens_mistral': 1073, 'n_tokens_neox': 932, 'n_words': 242}