Needed to interface with the RAMQ

Closed Posted 3 years ago Paid on delivery
Closed Paid on delivery

Deadline 1: October 15, 2020

End of support for versions 1.0 and 1.1 of the TLS (Transport Layer Security) protocol. Applications must support

version 1.2 of the TLS protocol by October 31, 2020. This phase will use the 2.0.0 version of the XSD schema.

Deadline 2: Jan 1, 2021

XSD schema version changes from 2.0.0 to 2.1.0.

For mid October 2020

Web Service Basic Profile 1.

Web Services Description Language 1.1 (WSDL)

Extensible Markup Language 1.0 (XML)

Unicode Transformation Format 8 (UTF-8)

Message Transmission Optimization Mechanism (MTOM)

Text Message Encoding 0

Simple Object Access Protocol 1.1 (SOAP)

Secure Sockets Layer 3.0 (SSL)

Transport Layer Security 1.2 (TLS protocol)

Hypertext Transfer Protocol – HTTP/1.1

The specifications for the RAMQ modual:

[login to view URL]

ID: AGP16148

PW:andxlog1a

(If asked to change PW: use "andxlog2a")

Tab: Facturation pour les professionnels de la santé;

DOCUMENTATION TECHNIQUE

Rémunération à l'acte via RFP (note "Trousse [login to view URL]")

AND

Autres modes de rémunération via Tip-I

"End of support for versions 1.0 and 1.1 of the TLS protocol

In order to ensure greater data protection, we inform you that RAMQ will end the

1.0 and 1.1 versions of the Transport Layer Security (TLS) protocol on October 31, 2020. This protocol

intervenes in the establishment of secure communications (HTTPS) to our services.

RAMQ asks all its partners to ensure that their infrastructure and applications support

version 1.2 of the TLS protocol by October 31, 2020."

Also note that:

Version number of the XSD schema changes from 2.0.0 to 2.1.0 QUOTE:

"Fact_serv_mdcal_spec_2_0_0

Fact_serv_mdcal_omni_2_0_0

Until this end date, we recommend that you change your version to the most recent, namely the ACTE version of the XSD schema with the following versions for the types of invoice:

Fact_serv_mdcal_omni_2_1_0

Fact_serv_mdcal_spec_2_1_0

Note that the latest version for the 5 agreements allows you to enter the diagnostic code in ICD-10.

For more details on this versioning policy, please consult chapter 1.1.3 and appendix 7 of the technical kit “Technical [login to view URL] ”.

I think the first step is to be able to send a claim as well as Generating Machin ID/PW and updating Machine PW.

I do generate the XML for TIP but not for RFP (the XSDs 2.1.0).

I am using Visual Foxpro, so maybe an EXE to call that can access the data I prepare (Flat files or DBFs), returned data could be droped into a text file.

If you know french, it would be great.

XML Visual Foxpro Web Security OpenSSL HTTP

Project ID: #27613268

About the project

Remote project Active 3 years ago